Re: Diagnosing NSString error in Leopard
Re: Diagnosing NSString error in Leopard
- Subject: Re: Diagnosing NSString error in Leopard
- From: John Stiles <email@hidden>
- Date: Wed, 05 Dec 2007 14:12:45 -0800
I take it back; joar's suggestion was right on the money. The breakpoint
caught the problem immediately.
I am used to Cocoa exceptions landing me in the debugger, since on Tiger
I had set up a bunch of breakpoints on known trouble spots. I had
forgotten to set this up on Leopard, though :)
Cool! Problem solved.
John Stiles wrote:
I don't think it's throwing, though.
(I managed to catch it with a well-placed assertion, FWIW, but I'd
still like to know.)
j o a r wrote:
On Dec 5, 2007, at 1:17 PM, John Stiles wrote:
What would be a good way to get the debugger to stop when this error
actually occurs?
A breakpoint on objc_exception_throw should do the trick, right?
j o a r
_______________________________________________
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
_______________________________________________
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