Usually, the easiest bugs to correct are the ones that predictably (repeatably) crash the application. I always tell junior programmers that crashing bugs are GOOD during development. Subtle "just not working right but doesn't crash" bugs are the WORST! That is one good reason to use the assertion macros in your code (to cause a crash close to the problem instead of later...)
Why are repeatable crash bugs good ? because you can very easily look at the stack trace in the debugger and or the stack trace in a core file and determine what went wrong.
Sadly, you have not provided the stack trace from the crash, so I can't help you. Fortunately, you probably don't need my help: The answer is right there in the debugger for you to see.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/email@hidden
This email sent to email@hidden
