From: Thomas Huth <1923693@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1923693] Re: Lack of architecture in gdbstub makes debugging confusing
Date: Fri, 30 Apr 2021 09:18:37 -0000 [thread overview]
Message-ID: <161977431724.11589.18042089205032132367.malone@soybean.canonical.com> (raw)
In-Reply-To: 161836759211.17765.12297179006766447607.malonedeb@wampee.canonical.com
Is there still anything left to do here?
** Changed in: qemu
Status: Fix Committed => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1923693
Title:
Lack of architecture in gdbstub makes debugging confusing
Status in QEMU:
Incomplete
Bug description:
I spent some quality time debugging GEF and came to a conclusion here:
https://github.com/hugsy/gef/issues/598#issuecomment-819174169
tldr;
* gdb_arch_name was undefined on riscv
* this bug was fixed recently via https://github.com/qemu/qemu/commit/edf647864bdab84ed4b1a4f47ea05be6bb075c69
* An undefined gdb_arch_name results in qemu's gdbstub omitting the <architecture> xml.
* gdb translates a missing <architecture> as "auto" which breaks a lot of stuff.
* tracking down where "auto" comes from is a bit confusing and time consuming.
It might be better to report a missing / blank gdb_arch_name as "<architecture>unknown</architecture>" instead of omitting the block completely.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1923693/+subscriptions
next prev parent reply other threads:[~2021-04-30 9:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-14 2:33 [Bug 1923693] [NEW] Lack of architecture in gdbstub makes debugging confusing kallisti5
2021-04-14 22:22 ` [Bug 1923693] " Alistair Francis
2021-04-30 9:18 ` Thomas Huth [this message]
2021-06-30 4:17 ` Launchpad Bug Tracker
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=161977431724.11589.18042089205032132367.malone@soybean.canonical.com \
--to=1923693@bugs.launchpad.net \
--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).