Re: Project fails to attach...
Re: Project fails to attach...
- Subject: Re: Project fails to attach...
- From: Roland King <email@hidden>
- Date: Mon, 06 Jun 2011 22:13:23 +0800
I've tried that and it didn't work, in the same way that running an app and turning on breakpoints later doesn't always work. Adding an exception handler at the top level has caught exceptions I just didn't catch before. Tried exception breakpoint and that hasn't worked out too well either. I like the top-level try-catch because it gets triggered whatever happens, whatever mode I'm in and it's been useful for me, sim, device debug .. it's kicked in. It is definitely a bit crude and perhaps I wouldn't ship it in a running app but I like an outer catch and log
Catch, log at the top level has been a lifesaver for me.
On 06-Jun-2011, at 9:50 PM, Matt Neuburg wrote:
>
> On Jun 6, 2011, at 6:18 AM, Roland King wrote:
>
>> I've taken to wrapping the main call in all my apps in a try-catch with a log for any exceptions.
>
> This seems a bit over the top. Why not just use an exception breakpoint? Set it to Exception All, Break On Throw, and there you are. Moreover you can promote it to a User breakpoint and now it's present universally in all your projects. I have such a universal exception breakpoint - but it wasn't switched on, because it never occurred to me that my code might be crashing; I thought something was wrong with Xcode. m.
>
> --
> matt neuburg, phd = email@hidden, http://www.apeth.net/matt/
> pantes anthropoi tou eidenai oregontai phusei
> Among the 2007 MacTech Top 25, http://tinyurl.com/2rh4pf
> Programming iOS 4! http://www.apeth.net/matt/default.html#iosbook
> RubyFrontier! http://www.apeth.com/RubyFrontierDocs/default.html
> TidBITS, Mac news and reviews since 1990, http://www.tidbits.com
>
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden