[Lldb-commits] [lldb] [lldb] Change lldb's breakpoint handling behavior (PR #96260)

[Jason Molenda via lldb-commits]

jasonmolenda wrote:

With my patch from this PR applied, the Mach Exception from debugserver is interpreted the same way -- it could be a watchpoint, a breakpoint, or an "instruction step", we use the address included in the ME to say which one it is, and in the ambiguous instance of instruction stepping to a BreakpointSite, we will incorrectly say we hit the breakpoint.

I haven't found the mechanism that an armv7 lldb-server would report `reason:trace` when it emulated the current instruction, put a breakpoint on the next instruction we'll execute, and 'continued' the thread when we resume.  But I might have just missed something in ProcessNativeLinux where it knows it was instruction stepping.  (but in the old stepping model in lldb, when you're at a BreakpointSite, the stop reason would be "breakpoint hit" even if it hadn't actually been hit)

https://github.com/llvm/llvm-project/pull/96260