[Lldb-commits] [PATCH] D16825: [Windows] Set correct thread stop info when single-step lands on a breakpoint

[Adrian McCarthy via lldb-commits]

amccarth added a comment.

In http://reviews.llvm.org/D16825#342279, @jingham wrote:

> Yes, it has always been this way.  Whenever we are about to start up the target - for whatever reason, we check to see if there is a breakpoint at the instruction where we are starting and if so we push a "ThreadPlanStepOverBreakpoint" which removes the breakpoint, puts in the correct instruction, single steps that thread and then replaces the breakpoint and continues.


Thanks for the confirmation.  I'm still not sure how TestConsecutiveBreakpoints.py used to work on Windows, but I believe this is the right fix.


http://reviews.llvm.org/D16825