Open Radar

 
Summary:
xcode/gdb stops at a breakpoint but indicates that it is stopped at the previously executed autocontinue breakpoint in all source code views and (3.2.x) when querying in the gdb console. xcode/gdb does not correct itself until you step over or into a line.

Steps to Reproduce:
- add a breakpoint and set its action to log some information including values of one or more variables in scope at the break point, and set it to continue
- add a simple breakpoint on a line you want to stop at.
- ensure:
    - both breakpoints are in the same file (it might also happen when they are in different files - not certain)
    - the autocontinue breakpoint must be reached first
    - the source files are open in different windows

Expected Results:
- when I break at the simple breakpoint, it should show me that breakpoint in source code and I should be able to confirm it via the gdb console

Actual Results:
- xcode indicates (by means of smaller arrow on top of breakpoint arrow) that the executable is stopped at the last autocontinue breakpoint that was hit (even though it is not stopped there)
- this happens both 
a) when the executable is still running
b) when the executable is stopped at a different simple breakpoint (in a different function many lines away)

Regression:
This has been happening in all xcode 3.2.x and possibly 3.1.x. I had hoped that it was fixed in 4.x, but as I'm a late upgrader, I've only just found out that its not fixed. I can't verify in 4.2 because it won't build my project at the moment.

Notes:
(I've had lots of failed debugging sessions, wasted time and frustration with this bug over the last few years (on several different machines), but haven't been able to pin it down so precisely before now.)