Skip to content

gdbstub: Protect gdb_handlesig() with EXCLUSIVE_GUARD()

Ilya Leoshkevich qemu-devel 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest3 patches 0 repliesNew

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/3cpu: Set current_cpu early in qemu-userbsd-user/main.c linux-user/main.c linux-user/syscall.c+5 -00 replies
2/3cpu: Introduce EXCLUSIVE_GUARD()include/hw/core/cpu.h+11 -00 replies
3/3gdbstub: Protect gdb_handlesig() with EXCLUSIVE_GUARD()gdbstub/user.c+2 -00 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH 0/3] gdbstub: Protect gdb_handlesig() with EXCLUSIVE_GUARD()

Hi,

I ran into the issue with only one thread being stopped on a breakpoint hit [1] again [2]. While a proper solution to this includes kicking all threads using a reserved host signal and parking them, and is partially in review and partially in the works, this small series resolves most of the problems that occur during a typical debugging session. Furthermore, it is a subset of the ultimate solution and therefore would not have to be reverted.

Best regards,
Ilya

[1] https://gitlab.com/qemu-project/qemu/-/issues/2465
[2] https://lore.kernel.org/qemu-devel/[email protected]/

Ilya Leoshkevich (3):
cpu: Set current_cpu early in qemu-user
cpu: Introduce EXCLUSIVE_GUARD()
gdbstub: Protect gdb_handlesig() with EXCLUSIVE_GUARD()

 bsd-user/main.c       |  2 ++
 gdbstub/user.c        |  2 ++
 include/hw/core/cpu.h | 11 +++++++++++
 linux-user/main.c     |  2 ++
 linux-user/syscall.c  |  1 +
 5 files changed, 18 insertions(+)
Signature · 1 line
2.47.1