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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

>> 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

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@xxxxxxxxxxxxxxxxx
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies



[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux