Open Radar

 
Summary:
Xcode decides to start Running when I tell it to Step too quickly.  Yes, technically, "running" is merely "stepping" very fast, but Xcode should not interpret my commands in this manner.

Steps to Reproduce:
1. I have a method with breakpoints configured as shown in the attached screenshot (<http://is.gd/o48IDB>).
2. The first breakpoint gets hit.
3. I start single-stepping through the code (I have mapped ^-S to the Product > Debug > Step Over command).
4. I start stepping rapidly, like maybe 5 - 10 times in rapid succession (I am NOT holding down the keys, so no auto-repeat).
5. Before I can exit the for-loop (as shown in the attachment) Xcode has decided to Run, instead of listening to my repeated Step commands.
6. Furthermore, Xcode seems to have become detached from the running executable, as none of the remaining breakpoints are hit, nor can I Stop the executable from Xcode anymore (pressing the Stop button does absolutely nothing).  I have to force-quit Xcode to make it start behaving again.

Update: Instead of using a key command in #3, rapidly clicking the step-over button in the debugger toolbar behaves the same way: many fast clicks in a row causes it to start running instead of continuing to step.

Expected Results:
I would expect Xcode to respect my commands, as described above.

Actual Results:
It doesn't, as described above.  BTW, this is with LLDB; not sure if it happens with GDB or not.

Regression:
I can never recall this ever happening in Xcode 3.x.

Notes: