but that seems to mainly refer to the qemu machine emulation.
I added -ggdb to QEMU_CFLAGS in config-host.mak so it builds with debug symbols but gdb still doesn't provide any useful information beyond the following:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffefdaf5700 (LWP 11211)]
0x0000000060363b58 in static_code_gen_buffer ()
(gdb) bt
#0 0x0000000060363b58 in static_code_gen_buffer ()
#1 0x00000000f50ba518 in ?? ()
#2 0x00000000624a9360 in ?? ()
#3 0x00007ffefdaf4b80 in ?? ()
#4 0x326cebdf4a8e4700 in ?? ()
#5 0x00007ffe00000000 in ?? ()
#6 0x0000000000000000 in ?? ()
What's the best way to debug the qemu user space emulation? I read this:
http:// wiki.qemu. org/Documentati on/Debugging
but that seems to mainly refer to the qemu machine emulation.
I added -ggdb to QEMU_CFLAGS in config-host.mak so it builds with debug symbols but gdb still doesn't provide any useful information beyond the following:
Using host libthread_db library "/lib/x86_ 64-linux- gnu/libthread_ db.so.1" .
[New Thread 0x7ffefdb6b700 (LWP 11210)]
[New Thread 0x7ffefdaf5700 (LWP 11211)]
[New Thread 0x7ffefda7f700 (LWP 11212)]
[New Thread 0x7ffefda09700 (LWP 11213)]
[New Thread 0x7ffefd993700 (LWP 11214)]
Program received signal SIGSEGV, Segmentation fault. 0363b58 in static_ code_gen_ buffer () code_gen_ buffer ()
[Switching to Thread 0x7ffefdaf5700 (LWP 11211)]
0x000000006
(gdb) bt
#0 0x0000000060363b58 in static_
#1 0x00000000f50ba518 in ?? ()
#2 0x00000000624a9360 in ?? ()
#3 0x00007ffefdaf4b80 in ?? ()
#4 0x326cebdf4a8e4700 in ?? ()
#5 0x00007ffe00000000 in ?? ()
#6 0x0000000000000000 in ?? ()
and valgrind doesn't help either.