phantom break points, erratic display
phantom break points, erratic display
- Subject: phantom break points, erratic display
- From: Frank Rimlinger <email@hidden>
- Date: Sun, 26 Sep 2004 14:59:53 -0400
I have been trying to find Xcode workarounds for the here-and-now,
short of always rebuilding the project. The one thing that still
bothers me are phantom breakpoints. This means the debugger thinks
there is a breakpoint but none appears in the breakpoint window. I
think this happens because you delete code where a real breakpoint used
to be. For whatever reason, the breakpoint fails to die, but now there
is no way to get rid of it. At least short of rebuilding the project.
Does anybody know where these breakpoints are cached?
Also, does anybody know why sometimes when you open the drop flag of a
variable in the debugger, examine the contents, and then close the drop
flag, why does the contents fail to disappear? Even though the drop
flag closes. This bug has been around since day one. Sometimes the
trick of going to another view in the call chain and then coming back
to the problem view will clear up the situation, and sometimes it
won't. Are there any other tricks for this, short of just executing
the code again?
I am using Xcode 1.5 and OS X 10.3.5. I use Xcode for C++ debugging,
and I don't know of any better product to do this on the Mac. I use
Eclipse for java debugging now, but I have a "shadow" Xcode project to
edit the code with and do searches. The Eclipse/Xcode combo works well
for Java, and gets around the "Windows-centric" design limitations of
Eclipse.
frank
_______________________________________________
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