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

[Pavel Labath via lldb-commits]

labath wrote:

> I don't know what I'm going to do here, and besides armv7 this same problem will occur for a target that has no instruction-step primitive. Another common trick is to have enough instruction emulation that you can tell what instruction will execute next by decoding the current instruction, and putting a breakpoint there. That has the same effect as armv7's instruction-step-by-breakpoints -- the reported stop reason from the stub will be "breakpoint hit".

FWIW, lldb-server already does this breakpoint-on-next-instruction dance for arm32 (and other architectures), but I'm not sure what kind of stop reason is reported in this case. Maybe @DavidSpickett has an arm32 machine around for a quick test? I think it'd be pretty easy to change the reported reason to something else in this case, if that helped.

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