Objc Msg error when i release mutable array which can have another array

[santhoshbabun]

I am developing an application in which one of the main object store Mutable array of objects...

@interface MainObject : NSObject {
	
	NSMutableArray *subObject;

}

@property(nonatomic,retain) NSMutableArray * subObject;

Sub Object is as follows

@interface SubObject : NSObject {
	
	NSMutableArray *finalObject;
	NSString *somestring;
}

@property (nonatomic,retain) NSMutableArray * finalObject;
@property (nonatomic,retain) NSString * somestring;

I have a table view and based on selection in there i will fill in the MainObject and when user goes back and do a diffrent selection i query the sql and need to store diffrent object...

I am trying to release it and create a new object and store the new values in the main object....

But it is failing in the dealloc of the SubObject with objc_msgSend error..

When i debugged i found that the as soon as the finalObject in the SubObject Class is released its other member somestring is also getting released....Although the address for the two are not the same.

Can someone plz help me to resolve this...

Thanks in Advance
Santhosh

[santhoshbabun]

I have attached the code base..... with the relavant classes. plz help me to resolve this....

[smasher]

Which object is failing in the dealloc? I can't find MainObject and SubObject in your project, so I don't know where to start looking.

You should be able to tell which line in the dealloc is causing the crash - is it [finalObject release] or [somestring release]? That will help you narrow your search also.

[dljeffery]

You shouldn't be calling [super dealloc] at the top of your dealloc implementations. That should be at the bottom, after you're done releasing your own stuff.

I don't know if it will actually cause any problems... very light testing on my own code, modified to put [super dealloc] at the top, didn't result in crashes. But you should still fix it. Honestly, it *feels* like putting it at the top of your dealloc should cause crashes, even though I didn't happen to hit any when trying it.

Also, try setting NSZombieEnabled to YES. And take a look at this as well:

Hamster Emporium: [objc explain]: So you crashed in objc_msgSend()