Re: breakpoints sometimes stop at the beginning of a C++ method
Re: breakpoints sometimes stop at the beginning of a C++ method
- Subject: Re: breakpoints sometimes stop at the beginning of a C++ method
- From: Steve Sisak <email@hidden>
- Date: Sat, 12 Feb 2005 10:58:30 -0500
At 5:51 PM +0000 2/11/05, email@hidden wrote:
> Why do breakpoints sometimes stop at the beginning of a C++ method
instead of the line where the breakpoint is set?
Similarly, while stepping through code, the graphical instruction pointer
(not to be confused with the real IP) is often a line or more behind. I
have to rely on watching variables change to red to tell me what line is
really being executed.
This happens to me on a daily basis -- it appears the Xcode is overly
aggressive in caching the mappings between file position and symbols
in memory while it's running.
This appears to during normal development over a number of
edit/debug/compile cycles -- I have suspicion that editing files
while your executable is still running in the debugger may be
involved.
In any case, the workaround is to simply quit and relaunch Xcode when
it gets confused. (You may have to adjust any breakpoints you set
while it was out of sync)
This has cleared the problem in all cases I've seen.
Note: that no amount of re-indexing of doing clean build will help,
you need to quit the IDE -- i.e. it's an in-memory cache issue.
(There are are another class of problems where re-indexing the
project is the fix -- when cmd-double-click fails to find a symbol)
HTH,
-Steve
_______________________________________________
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