mirror of
https://github.com/cirosantilli/linux-kernel-module-cheat.git
synced 2026-01-23 02:05:57 +01:00
Document failed bisect of ARM kernel module debug
This commit is contained in:
@@ -873,13 +873,13 @@ A blunt resolution for QEMU is on host:
|
||||
....
|
||||
pkill qemu
|
||||
....
|
||||
* GDB step debugging of kernel modules broke at some point. This was noticed at 6420c31986e064c81561da8f2be0bd33483af598 and a likely candidate was the recent move to kernel v4.15, but this has to be bisected.
|
||||
+
|
||||
On GEM5, it is possible to use the `m5` instrumentation from guest as a good workaround:
|
||||
+
|
||||
....
|
||||
m5 exit
|
||||
....
|
||||
* GDB step debugging of kernel modules broke at some point. This happens at 6420c31986e064c81561da8f2be0bd33483af598 on kernel v4.15, 6b0f89a8b43e8d33d3a3a436ed827f962da3008a v4.14 and 5ad68edd000685c016c45e344470f2c1867b8e39 v4.12 and also if kernel 4.9.6 is checked out. So maybe it was never working in the first place, but we never noticed?
|
||||
+
|
||||
Just afte GDB connects, we get the following message from the kernel GDB Python scripts:
|
||||
....
|
||||
|
||||
Reference in New Issue
Block a user