On Tue, 7 Jul 2026 at 18:27, Richard Henderson <[email protected]> wrote: > > On 7/6/26 02:21, Peter Maydell wrote: > > No other architecture, CPU or board in QEMU needs to do this, > > so my instinct is to say that M-profile should not be special here. > > Richard, Alex: how do we usually handle breakpoint insns for the > > gdbstub ? > > We handle them via CPUBreakpoint structures; we never inject code changes.
I don't mean "breakpoints that the gdbstub requests", I mean "breakpoint insns that are already in the guest code that get executed". > The patch description explains the confusion: this is attempting to replicate > a feature of > the Raspberry Pi Pico SDK, wherein a guest BPKT really is trapped by an > external debugger. But aren't breakpoint instructions of all kinds typically trapped to the external jtag debugger, on any architecture ? I'm a bit surprised that we don't do this already. thanks -- PMM
