blob: 3e56f1c78a93feef267f0f04b4be7e02b5f341dc (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
|
debug: 0.827
graphic: 0.701
device: 0.607
semantic: 0.534
network: 0.509
performance: 0.461
permissions: 0.448
socket: 0.447
files: 0.400
vnc: 0.372
other: 0.323
KVM: 0.303
PID: 0.286
boot: 0.276
Lack of architecture in gdbstub makes debugging confusing
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.
Thanks for raising this. I have marked it as fixes as like you say it's fixed in mainline.
Is there still anything left to do here?
[Expired for QEMU because there has been no activity for 60 days.]
|