FROM : Andrew Duncan
DATE : Wed Aug 18 00:13:10 2004
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?
Andrew
_______________________________________________
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 00:13:10 2004
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?
Andrew
_______________________________________________
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

