Re: Application crashes with no calls tracing back to my code
Re: Application crashes with no calls tracing back to my code
- Subject: Re: Application crashes with no calls tracing back to my code
- From: Ken Thomases <email@hidden>
- Date: Sat, 27 Mar 2010 07:10:01 -0500
On Mar 27, 2010, at 7:00 AM, Ken Thomases wrote:
> On Mar 27, 2010, at 6:29 AM, Arun wrote:
>
>> My application is crashing sometimes with the following crash log. It has no
>> traces of my code. Can anyone look into the crash log suggest some ideas?
>
> Probably a memory management bug. You are over-releasing or under-retaining something. An NSImage, from the looks of things.
>
> http://www.sealiesoftware.com/blog/archive/2008/09/22/objc_explain_So_you_crashed_in_objc_msgSend.html
And beyond the advice at the link, I should have said to use the Zombie instrument or, the manual way, set NSZombieEnabled=YES and MallocStackLoggingNoCompact=YES, set a breakpoint in -[_NSZombie methodSignatureForSelector:], then when the debugger stops on that breakpoint, use "info malloc-history" command to figure out where the zombie was originally allocated.
http://www.friday.com/bbum/2010/01/10/using-malloc-to-debug-memory-misuse-in-cocoa/
http://developer.apple.com/mac/library/technotes/tn2004/tn2124.html
Also, use Xcode's Build and Analyze feature to see if the static analyzer can identify your memory management bugs.
Cheers,
Ken
_______________________________________________
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