blob: b75ee1a0e02723533bb1cc19fab6f3e5fa62bc09 (
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
40
41
42
43
44
45
46
47
48
49
50
51
52
53
|
debug: 0.257
semantic: 0.156
other: 0.117
graphic: 0.088
vnc: 0.057
device: 0.049
files: 0.045
performance: 0.041
permissions: 0.041
network: 0.039
PID: 0.032
boot: 0.028
socket: 0.026
KVM: 0.025
debug: 0.900
other: 0.018
files: 0.018
semantic: 0.017
PID: 0.007
boot: 0.006
device: 0.006
network: 0.006
performance: 0.005
socket: 0.005
vnc: 0.003
graphic: 0.003
permissions: 0.003
KVM: 0.002
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.]
|