Re: Uncaught exceptions not terminating my app
Re: Uncaught exceptions not terminating my app
- Subject: Re: Uncaught exceptions not terminating my app
- From: "Paul Sanders" <email@hidden>
- Date: Thu, 28 Jan 2010 15:17:51 -0000
Yes, I believe this is new in Snow Leopard. But on Leopard and
Tiger, only numerical addresses are available and to interpret
those requires that you know the 'slide' of each dylib loaded,
which varies from machine to machine.
Mind you, with the breathtaking speed of uptake of Snow Leopard,
maybe that is good enough...
Paul Sanders.
----- Original Message -----
From: "Scott Ribe" <email@hidden>
To: "Paul Sanders" <email@hidden>
Cc: <email@hidden>
Sent: Thursday, January 28, 2010 2:23 PM
Subject: Re: Uncaught exceptions not terminating my app
> If you don't crash the app, you don't get the stack trace. No
> stack trace = no clue about what went wrong.
Just yesterday I was working on some new code, which threw an
exception, and
the logged message included the stack trace. Never seen that
before, so I
assume it's new in Snow Leopard. At this point I have no idea
whether that's
true for all exceptions or just certain types, and whether or
not it
requires the developer tools to be installed.
But perhaps something to check into: examine logs for exceptions
thrown by
your app...
--
Scott Ribe
email@hidden
http://www.killerbytes.com/
(303) 722-0567 voice
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden