Re: Tips & Tricks for debugging difficult crashes?
Re: Tips & Tricks for debugging difficult crashes?
- Subject: Re: Tips & Tricks for debugging difficult crashes?
- From: Markus Hitter <email@hidden>
- Date: Wed, 13 Feb 2002 09:28:34 +0100
Am Mittwoch den, 13. Februar 2002, um 04:16, schrieb Adam Iser:
What's the best way to track down a crash that happens in 100%
system code?
1) Do a good guess based on the names of the methods in the backtrace.
2) Try to slim down your app to a minimum showing the bug.
3) Copy a backtrace here to the list and perhaps some piece of
code which might be causing this.
(you did 1 - 3 alrady)
4) File a bug report if your code appears to be valid.
My app has 2 threads, each with it's own run loop. The
secondary thread is nothing but an NSTimer scheduled to fire 4
times a second, take strings from an open socket, and stick
them in a shared que. The main thread then pulls these strings
out later on.
Are you sure this is an effective choice? Wouldn't it work using
-readInBackgroundAndNotify? Should make your second thread
obsolete.
Markus
- - - - - - - - - - - - - - - - - - -
Dipl. Ing. Markus Hitter
http://www.jump-ing.de/
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.