Thread (9 messages) 9 messages, 4 authors, 2017-09-22

Any successful story of debugging linux 4.13 with qemu 2.10 and gdb 8.01?

From: Saket Sinha <hidden>
Date: 2017-09-21 07:29:57

Hi,
quoted
Without being too long, the problem is KALSR. You have to disable it
disabling the kernel option "Randomize the address of the kernel image (KASLR)",
inside Processor type and features. In this way, gdb can translate
all the symbols correctly (symbols <-> addresses).

I really don't know how the developers test their code... because there
is no evidence for this.
Why do you think that it requires developers to use a debugger and qemu
to test their code?  I've never used a debugger on the kernel in all of
my years of kernel development...
I agree the developers should not be doing it.

It is documented that gdb/kgdb will not work if KALSAR is enabled.

Please refer -
https://github.com/torvalds/linux/commit/e604f1cb85367d2e5fd4cf253296d190996da81a


Regards,
Saket Sinha
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help