Re: How to find EXC_BAD_ACCESS bug?

FROM : Nick Zitzmann
DATE : Wed Aug 18 01:16:39 2004

On Aug 17, 2004, at 5:03 PM, Andrew Duncan wrote:

> Thanks Nick; at this point I think the backtraces are just too
> different each time to really help. (I may be wrong about this
> though.)
>
> But on a related note, the debugger log suggests
>
>  Try setting environment variable MallocHelp to see tools to help
> debug
>
> So what environment is it talking about?


Your application probably has a memory problem somewhere. If it's
crashing in NSPopAutoreleasePool(), that means the application
deallocated an object that was in the autorelease pool. If you're
seeing console errors about double-free() calls, that means exactly
what it says. If it's crashing in objc_msgSend(), that means a message
was sent to an object that was deallocated at some point. Backtraces in
this case can be more important than you may think...

Nick Zitzmann
<http://www.chronosnet.com/>
_______________________________________________
cocoa-dev mailing list | <email_removed>
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.