From: "Alex Bennée" <alex.bennee@linaro.org>
To: pbonzini@redhat.com
Cc: qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>
Subject: [Qemu-devel] [PATCH v4 0/4] some gdbstub fixes for debug and vcont
Date: Wed, 12 Jul 2017 11:52:12 +0100 [thread overview]
Message-ID: <20170712105216.747-1-alex.bennee@linaro.org> (raw)
Hi Paolo,
I was going through my review queue and realised I had this hanging
around with an outstanding comment. Basically the only change is to
fix the bsd-user build by adding a field for the thread-id. It isn't
populated but it never was and it looks like the gdbstub for threaded
bsd-user programs has been broken forever.
Given the range of different ways of getting a thread-id and the fact
the bsd fork machinery looks like it needs updating anyway I'd left
this for a future BSD maintainer to fix up properly.
Are you happy to take this into your tree?
Alex Bennée (4):
gdbstub: modernise DEBUG_GDB
gdbstub: rename cpu_index -> cpu_gdb_index
qom/cpu: remove host_tid field
gdbstub: don't fail on vCont;C04:0;c packets
bsd-user/qemu.h | 2 +
gdbstub.c | 117 ++++++++++++++++++++++++-------------------------
include/exec/gdbstub.h | 9 ----
include/qom/cpu.h | 2 -
linux-user/syscall.c | 1 -
5 files changed, 59 insertions(+), 72 deletions(-)
--
2.13.0
next reply other threads:[~2017-07-12 10:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 10:52 Alex Bennée [this message]
2017-07-12 10:52 ` [Qemu-devel] [PATCH v4 1/4] gdbstub: modernise DEBUG_GDB Alex Bennée
2017-07-12 10:52 ` [Qemu-devel] [PATCH v4 2/4] gdbstub: rename cpu_index -> cpu_gdb_index Alex Bennée
2017-07-12 10:52 ` [Qemu-devel] [PATCH v4 3/4] qom/cpu: remove host_tid field Alex Bennée
2017-07-12 10:52 ` [Qemu-devel] [PATCH v4 4/4] gdbstub: don't fail on vCont; C04:0; c packets Alex Bennée
2017-07-12 11:43 ` [Qemu-devel] [PATCH v4 0/4] some gdbstub fixes for debug and vcont Philippe Mathieu-Daudé
2017-07-12 16:34 ` Paolo Bonzini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170712105216.747-1-alex.bennee@linaro.org \
--to=alex.bennee@linaro.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).