[Lldb-commits] [PATCH][Please review] Check StopInfo instead of pc/breakpointsite to determine if we are at a breakpoint

Kopec, Matt matt.kopec at intel.com
Mon Sep 10 13:33:23 PDT 2012

Problem: If there are breakpoints on consecutive instructions, the debugger doesn't stop on the consecutive breakpoints after the first breakpoint.

After hitting the first breakpoint and then stepping/continuing, the step over breakpoint plan will be pushed to the plan queue for the next consecutive breakpoint (the first breakpoint has been stepped over and pc incremented). This will cause lldb to step over the next consecutive breakpoint and run without actually stopping on the breakpoint(s).

On a side note, is there a specific reason for checking the pc/breakpointsite list instead of the stop reason?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-commits/attachments/20120910/0904ddfb/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: consecutive-bp-inst-fix.patch
Type: application/octet-stream
Size: 1040 bytes
Desc: consecutive-bp-inst-fix.patch
URL: <http://lists.llvm.org/pipermail/lldb-commits/attachments/20120910/0904ddfb/attachment.obj>

More information about the lldb-commits mailing list