Re: XCode Debug Exception problem
Re: XCode Debug Exception problem
- Subject: Re: XCode Debug Exception problem
- From: Keary Suska <email@hidden>
- Date: Wed, 06 Mar 2013 08:11:24 -0700
On Mar 6, 2013, at 6:10 AM, Dave wrote:
> I wondering if this a bug, a feature or some option I can't find!
>
> When I am stepping through my code and it causes an exception, the debugger jumps me off into some assembler code and seems to lose the stack trace of where it was called from so I can go back and see what caused the problem.
>
> This used to work fine in XCode 3, it doesn't seem to work any more in the version of 4.6 of XCode???
>
> Is there something I am missing?
I think the difference is GDB vs LLDB. In my experience, GDB was far more stable and reliable than LLDB, although not as full featured. I find almost every time if I poke around the call stack too much (which could be as little as three of four clicks) that LLDB will get confused and refuse to print any objects that are clearly in scope. And if an exception occurs while in the debugger--forget it. LLDB gets completely lost and you can only restart your session.
On the other hand, there are a number of reasons why it might be reasonable for the debugger to act in this way. Exception handling is a tricky business, and if you add in multi-threading...
Anyway, there is not likely much you can do except try to circle around the exception until you can figure out what it is and solve it.
HTH,
Keary Suska
Esoteritech, Inc.
"Demystifying technology for your home or business"
_______________________________________________
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