Re: Debugging objc_msg errors
Re: Debugging objc_msg errors
- Subject: Re: Debugging objc_msg errors
- From: Corbin Dunn <email@hidden>
- Date: Wed, 14 Jan 2009 16:14:41 -0800
On Jan 14, 2009, at 11:04 AM, John Nairn wrote:
I occasionally get difficult-to-debug crashes where that last thing
in the crash log is a message being sent, which ends up being a
message sent to an object that has been released (I think it is
objc_msg, but I am not looking at a crash log now). These happen
much more often in Leopard than in Tiger.
Since I have many messages going to many objects, it can take me a
long time to track these problems down (in one case several weeks).
I am fairly certain it is not a notification message because I also
remove objects as observers before they are deallocated. Is there a
debugging tool that can provide more information about what message
was sent to what object at the time of the crash?
What the others have posted is good, but IMHO the easiest way to debug
overreleased objects is with Instruments. You frequently want to know
where the over release was.
http://www.corbinstreehouse.com/blog/index.php/2007/10/instruments-on-leopard-how-to-debug-those-random-crashes-in-your-cocoa-app/
corbin
_______________________________________________
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