Received: from eggs.gnu.org ([2001:4830:134:3::10]:51239) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZIgD7-0001AA-7C for qemu-devel@nongnu.org; Fri, 24 Jul 2015 12:52:37 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZIgD3-0006a9-Qp for qemu-devel@nongnu.org; Fri, 24 Jul 2015 12:52:37 -0400 From: Jan Kiszka Message-ID: <55B26D4F.3040108@siemens.com> Date: Fri, 24 Jul 2015 18:52:31 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] [PATCH] gdbstub: Set current CPU on interruptions List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-trivial Cc: qemu-devel gdb expects that the thread ID for c and g-class operations is set to the CPU we provide when reporting VM stop conditions. If the stub is still tuned to a different CPU, the wrong information is delivered to the gdb frontend. Signed-off-by: Jan Kiszka --- gdbstub.c | 1 + 1 file changed, 1 insertion(+) diff --git a/gdbstub.c b/gdbstub.c index 92b2f81..ffe7e6e 100644 --- a/gdbstub.c +++ b/gdbstub.c @@ -1285,6 +1285,7 @@ static void gdb_vm_state_change(void *opaque, int running, RunState state) ret = GDB_SIGNAL_UNKNOWN; break; } + gdb_set_stop_cpu(cpu); snprintf(buf, sizeof(buf), "T%02xthread:%02x;", ret, cpu_index(cpu)); send_packet: -- 2.1.4