Re: debugger wonkiness
Re: debugger wonkiness
- Subject: Re: debugger wonkiness
- From: Don Quixote de la Manvha <email@hidden>
- Date: Wed, 02 May 2012 18:40:29 -0700
I've seen this happen too, but I'm pretty sure it was with GDB and not lldb. I'm not dead certain as it has been a while, but if we are experiencing the same bug then it's in Xcode and not either of the debuggers.
Please file a report at http://bugreport.apple.com/
At the same time make a tarball of your whole project. You want to be sure you can get back to the code that stimulated the bug.
If at all possible make a minimal test case and attach it to the bug. That may not be possible for valid reasons. If you cannot make a test case, say so in your report.
Coders always want test cases but sometimes we can't get them. Next best is lots of reports from lots of people. Maybe one fan elicit the common thread.
This isn't going to fix your problem anytime soon. To debug when the debugger won't work, use NSLog, printf, NSAssert, assert, Design by Contract, Class Invariants, and in-memory circular log buffers that dump there contents when doing so won't be disruptive.
I successfully wrote an AES hard drive encryptor in assembly code for an ARM embedded target for which my only "debugger" was a bank of eight LEDs that I could toggle on or off by setting bits in a byte at a certain fixed address. That's It.
If I can do that, you can debug your app without a source debugger.
Don Quixote
Sent from my iPhone
On May 2, 2012, at 12:14 PM, John Michael Zorko <email@hidden> 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:
>
> 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