On Dec 11, 2008, at 1:30 PM, Markus Spoettl wrote:
On Dec 11, 2008, at 1:11 PM, j o a r wrote:
Overwrite GFController's -release and -autorelease, simply calling
[super release] and [super autorelease] (ensure you get the
signatures exactly right). Set a breakpoint in both and debug the
app. When the debugger hits the breakpoints you will see exactly
who called it in the call stack. You can then go a figure out if
that was on purpose.
Don't do that - Use the ObjectAlloc Instrument, it provides this
information out of the box.
So it stops the debugger and shows you the call stack *at the exact
time it's being called* and gives to an opportunity to walk back the
call stack before continuing? How so? Please do tell me how to do
that.
Sure does! (obviously, aside from stopping the debugger..)
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 (Cocoa-dev@lists.apple.com)
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
