qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: Ilya Leoshkevich
Subject: [PATCH 0/3] gdbstub: Protect gdb_handlesig() with EXCLUSIVE_GUARD()
Date: Mon, 13 Jan 2025 14:36:26 +0100

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] 
6d1171d8debb462f468bb47ff875e0e9db253b4e.camel@linux.ibm.com/">https://lore.kernel.org/qemu-devel/6d1171d8debb462f468bb47ff875e0e9db253b4e.camel@linux.ibm.com/

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(+)

-- 
2.47.1




reply via email to

[Prev in Thread] Current Thread [Next in Thread]