Re: The case of the broken breakpoints
Re: The case of the broken breakpoints
- Subject: Re: The case of the broken breakpoints
- From: Quincey Morris <email@hidden>
- Date: Thu, 31 Dec 2009 14:57:43 -0800
On Dec 31, 2009, at 14:27, Ken Thomases wrote:
> On Dec 31, 2009, at 3:51 PM, Oftenwrong Soong wrote:
>
>> Under some circumstances (and I cannot yet define exactly what those circumstances are), it appears that Xcode suddenly decides to ignore breakpoints, meaning that gdb does not pause execution on lines where I place a breakpoint.
>
> One thing you don't mention is turning off "Load symbols lazily" in Xcode's preferences (under Debugging). That's been noted as a frequent culprit in situations like this.
We're talking about two different things here.
Sometimes the breakpoint marker is blue and the debugger won't stop at breakpoints. I *think* that's a scenario where the lazy symbol loading can be the culprit. Also, since 10.6 at least, I've seen cases where blue breakpoints aren't honored until a new breakpoint is set/cleared somewhere one time (in the same Xcode session? -- it's not clear).
Sometimes the breakpoint marker is orange/yellow and that means Xcode *knows* the breakpoints won't be honored. In the past, I believe I've seen this transiently, but in the OP's case, where they simply wouldn't go back to blue, it might have been something mundane but obscure, like the debugger already being hung up on a process from a previous debugging session. It's a little hard to diagnose, because the process may not be easily visible. But that's pretty much pure speculation.
_______________________________________________
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