Re: debugger wonkiness
Re: debugger wonkiness
- Subject: Re: debugger wonkiness
- From: Dave <email@hidden>
- Date: Thu, 03 May 2012 22:15:28 +0100
I get this too and the only way I've found to make it work it to
manually put a breakpoint in the delegate, a thought was maybe change
the optimization level for the debug version?
Hope this helps
Dave
On 2 May 2012, at 20:14, John Michael Zorko wrote:
Hello, all ...
This happens to me a _lot_ when debugging ... i'll put a breakpoint
on a delegate callback, and when said breakpoint is reached, i'll
try to step into said delegate callback. The object is valid, but
what usually happens is that the debugger just goes away i.e.
control never comes back to me, the app is still hung at said
breakpoint, etc. and I have to restart debugging and hope it works
next time. This has happened ever since the early days of Xcode4
(i'm on 4.3 on Lion now) so i'm wondering if there's something I
can do to fix this. It doesn't happen exclusively on delegate
callbacks (i've also occasionally seen it trying to step into for
loops) but it happens a _lot_ with delegate callbacks.
This is debugging an app under iOS 5.1, using lldb. Any help would
be appreciated -- my Xcode4 experience would be much nicer if the
debugger didn't do this :-)
Regards,
John
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40looktowindward.com
This email sent to email@hidden
_______________________________________________
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