Re: program termination after releasing self defined NSXMLParser class
Re: program termination after releasing self defined NSXMLParser class
- Subject: Re: program termination after releasing self defined NSXMLParser class
- From: Jens Alfke <email@hidden>
- Date: Fri, 16 Apr 2010 08:34:51 -0700
On Apr 16, 2010, at 2:58 AM, Dominic Dauer wrote:
> After I entered bt or backtrace I got the following message:
>
> Program received signal: “EXC_BAD_ACCESS”.
> #0 0x93e0bedb in objc_msgSend ()
> #1 0x00000000 in ?? ()
>
> This is all.
OK, that means the stack got corrupted before the crash. Makes it harder to debug.
1. Are you certain that it’s the -release call doing this? Have you single-stepped through the code?
2. Did you try running the static analyzer (via the Build menu)?
3. Try setting the environment variables “MallocScribble” and “MallocPreScribble” (in the Arguments tab of the Executable inspector.) These will cause malloced and freed blocks to be overwritten with 0xBB and 0x55, which makes it more likely that bad code will crash earlier and in a more obvious way.
—Jens_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden