Re: What is up with the failure to indicate when execution has stopped at a breakpoint?
Re: What is up with the failure to indicate when execution has stopped at a breakpoint?
- Subject: Re: What is up with the failure to indicate when execution has stopped at a breakpoint?
- From: G S <email@hidden>
- Date: Wed, 15 Jun 2011 03:51:29 -0700
Thanks for the response.
> This annoying, but not a show-stopper. You can click on an entry in the backtrace and the source code display should right itself (or, at worst, click a different entry and back to the desired one). Is this what's happening to you?
No. If it were that simple, I would have filed a bug (which I did)
and moved on. None of the entries in the backtrace cause the source
display to budge, until you click on one that's in a different and
non-afflicted file. This problem afflicts one or more different files
at different times. It happens with both Objective-C and C++ files in
my iPhone project.
The project is pretty simple. The code isn't compiled into a library
or anything. It is being built for Debug.
> The other thing to keep in mind is that, if the level-of-detail slider below the backtrace isn't at its rightmost position, some backtrace entries might be hidden, and that's going to affect how the debugger orients itself in the source code. If enough detail is hidden, the debugger may appear to be really, really broken.
I had no idea what that unlabeled control was. I tried adjusting it,
but it didn't reveal anything that shed any light on this issue.
Regards,
Gavin
_______________________________________________
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