Instruments adds some extra safeguarding to some of their tools, so you should whittle down your functionality until you know this-or-that code will cause or not cause the crash, depending on inclusion. It's possible what you're seeing is a side-effect that is set up elsewhere and dies in a different place. Crashers typically are easier to track down, but some do require lots of detective work.
On 04/22/2010 8:20 AM, "Jerry Krinock" <je...@ieee.org> wrote: > Another reason I didn't get very far is that the only factor I was able to > isolate was using the Instruments' Threads performance tool. This definitely > causes the app to crash. More logging (NSLog) also seems to be inhibit > crashes. Possibly Jeff's demo apps crash more consistently because they do > very little logging. _______________________________________________ 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
