FROM : Stéphane Sudre
DATE : Wed Aug 18 21:35:01 2004
On mercredi, ao{t 18, 2004, at 12:13 AM, Andrew Duncan wrote:
> My Cocoa app regularly crashes with this bad access error, but every
> time I debug the app it (appears to) crash in a different place. Often
> this is buried way down in system routines, where the debugger shows
> only disassembled op codes. Sometimes this is purely in the NSApp's
> run loop, so there is none of my code on the stack. Sometimes it's in
> my code, but there's no obviously suspect code nearby.
>
> What are the basic tools/procedures for using Xcode to narrow this
> down?
Enable NSZombie.
You're probably releasing too much.
_______________________________________________
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.
DATE : Wed Aug 18 21:35:01 2004
On mercredi, ao{t 18, 2004, at 12:13 AM, Andrew Duncan wrote:
> My Cocoa app regularly crashes with this bad access error, but every
> time I debug the app it (appears to) crash in a different place. Often
> this is buried way down in system routines, where the debugger shows
> only disassembled op codes. Sometimes this is purely in the NSApp's
> run loop, so there is none of my code on the stack. Sometimes it's in
> my code, but there's no obviously suspect code nearby.
>
> What are the basic tools/procedures for using Xcode to narrow this
> down?
Enable NSZombie.
You're probably releasing too much.
_______________________________________________
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.






Cocoa mail archive

