From: Peter Xu <peterx@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
peterx@redhat.com
Subject: [PATCH 0/2] gdbstub: Unbreak i386 with gdb remote
Date: Thu, 9 Apr 2020 12:49:52 -0400 [thread overview]
Message-ID: <20200409164954.36902-1-peterx@redhat.com> (raw)
It's silently broken on master during an refactoring. Let's fix it.
Please feel free to drop patch 1 if it's not rc material, but I guess
we want patch 2...
Thanks,
Peter Xu (2):
gdbstub: Assert len read from each register
gdbstub: i386: Fix gdb_get_reg16() parameter to unbreak gdb
gdbstub.c | 11 ++++++++---
target/i386/gdbstub.c | 2 +-
2 files changed, 9 insertions(+), 4 deletions(-)
--
2.24.1
next reply other threads:[~2020-04-09 16:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-09 16:49 Peter Xu [this message]
2020-04-09 16:49 ` [PATCH 1/2] gdbstub: Assert len read from each register Peter Xu
2020-04-09 17:51 ` Philippe Mathieu-Daudé
2020-04-09 18:12 ` Peter Xu
2020-04-09 16:49 ` [PATCH 2/2] gdbstub: i386: Fix gdb_get_reg16() parameter to unbreak gdb Peter Xu
2020-04-09 17:21 ` Philippe Mathieu-Daudé
2020-04-09 18:01 ` Peter Xu
2020-04-09 19:29 ` Philippe Mathieu-Daudé
2020-04-09 20:36 ` Alex Bennée
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=20200409164954.36902-1-peterx@redhat.com \
--to=peterx@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=philmd@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).