* [Bug 1923693] [NEW] Lack of architecture in gdbstub makes debugging confusing
@ 2021-04-14 2:33 kallisti5
2021-04-14 22:22 ` [Bug 1923693] " Alistair Francis
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: kallisti5 @ 2021-04-14 2:33 UTC (permalink / raw)
To: qemu-devel
Public bug reported:
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.
** Affects: qemu
Importance: Undecided
Status: New
--
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:
New
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
^ permalink raw reply [flat|nested] 4+ messages in thread* [Bug 1923693] Re: Lack of architecture in gdbstub makes debugging confusing 2021-04-14 2:33 [Bug 1923693] [NEW] Lack of architecture in gdbstub makes debugging confusing kallisti5 @ 2021-04-14 22:22 ` Alistair Francis 2021-04-30 9:18 ` Thomas Huth 2021-06-30 4:17 ` Launchpad Bug Tracker 2 siblings, 0 replies; 4+ messages in thread From: Alistair Francis @ 2021-04-14 22:22 UTC (permalink / raw) To: qemu-devel Thanks for raising this. I have marked it as fixes as like you say it's fixed in mainline. ** Changed in: qemu Status: New => Fix Committed -- 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: Fix Committed 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 ^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug 1923693] Re: Lack of architecture in gdbstub makes debugging confusing 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 2021-06-30 4:17 ` Launchpad Bug Tracker 2 siblings, 0 replies; 4+ messages in thread From: Thomas Huth @ 2021-04-30 9:18 UTC (permalink / raw) To: qemu-devel 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 ^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug 1923693] Re: Lack of architecture in gdbstub makes debugging confusing 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 @ 2021-06-30 4:17 ` Launchpad Bug Tracker 2 siblings, 0 replies; 4+ messages in thread From: Launchpad Bug Tracker @ 2021-06-30 4:17 UTC (permalink / raw) To: qemu-devel [Expired for QEMU because there has been no activity for 60 days.] ** Changed in: qemu Status: Incomplete => Expired -- 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: Expired 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 ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2021-06-30 4:26 UTC | newest] Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 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 2021-06-30 4:17 ` Launchpad Bug Tracker
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).