Greg Parker wrote:

> You might try installing an @try/@catch block in main. If the unwinder is 
> working long enough to get there then you can log something to help debug 
> further. You can use `...@catch (NSException *e)` to check for Objective-C 
> exceptions and `...@catch (...)` to check for C++ exceptions.

Excellent, thanks for all the info and the suggestion. I’ll do this and see if 
anything drops out of it.


vincent habchi wrote:

> By the way, both thread 0 and 2 seem to be in the same routine by the time it 
> crashes. Are you sure all your variables are thread safe?

That function is CFRunLoopRun, which is explicitly meant for use on different 
threads. (Yes, they’re separate run loops.)


Joar Wingfors wrote:

> The default system compiler on Mac OS X is GCC, not LLVM.

True enough, but Xcode and other non-trivial apps are compiled with LLVM, and 
for quite some time the message out of Apple’s devtools team has been to 
migrate to LLVM. I even seem to recall hearing at WWDC that the only reason 
they didn’t change the default compiler in some recent version of Xcode was 
because it just seemed wrong to do that in a maintenance release. I still can’t 
use pure LLVM due to Clang bugs, but GCC LLVM (which is what devtools 
advocates) appears to be working well.


Roland King wrote:

> Adding a try/catch around some main bits of the app found the real issue for 
> me. 

Another good suggestion, thanks. This may be a bit hard for me, because this 
app has a lot of dispatching to the main thread, but between Greg’s suggestion 
and yours, perhaps I can get a critical clue logged.


Thanks, everyone. I’ll give it all a shot and we’ll see how it goes.

Benjamin Rister_______________________________________________

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

Reply via email to