You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Update debuginfo dexter stepping for new lldb behavior
dexter sets breakpoints on every source line in the file.
Then it step-in's to every source line, and tests are written
to expect that one step will move between lines, hitting the
breakpoints that are set there.
With this new algorithm, lldb will now step to the next source
line, and be stopped at a breakpoint, but it has not yet hit the
breakpoint. The stop reason will be "step-in completed". When
you do "step-in" again, we will hit the breakpoint instruction,
stop with a "breakpoint-hit" stop reason -- but the pc has not
advanced. Then when you "step-in" again, we will move to the
next source line.
In short, lldb needs to step twice in a situation with breakpoints
on every source line and stepping across them.
This patch detects when lldb is behaving this way, and preserves
the behavior the tests expect. It will step-in, and if we stop
with a step-in stop reason and we are stopped at a breakpoint site,
we will step once again to hit the breakpoint.
0 commit comments