3rd-party/linux-kernel-module-cheat
1
0
Fork 0
mirror of https://github.com/cirosantilli/linux-kernel-module-cheat.git synced 2026-01-23 10:15:57 +01:00
Code Issues Releases Wiki Activity

readme: more uniform titles to gem5 step debug sections

Browse Source
This commit is contained in:
Ciro Santilli
2018-03-25 19:17:05 +01:00
parent 2656202dff
commit a1a6a5d6fb
1 changed files with 4 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
README.adoc
View File

@@ -2643,8 +2643,9 @@ Kernel command line:
....
[[gem5-gdb]]
=== gem5 GDB step debugging
=== gem5 GDB step debug
==== gem5 GDB step debug kernel
Analogous <<gdb,to QEMU>>, on the first shell:
....
@@ -2669,7 +2670,7 @@ And we now see the boot messages, and then get a shell. Now try the `/continue.s
TODO: how to stop at `start_kernel`? gem5 listens for GDB by default, and therefore does not wait for a GDB connection to start like QEMU does. So when GDB connects we might have already passed `start_kernel`. Maybe `--debug-break=0` can be used? https://stackoverflow.com/questions/49296092/how-to-make-gem5-wait-for-gdb-to-connect-to-reliably-break-at-start-kernel-of-th
==== gem5 GDB step debugging aarch64
===== gem5 GDB step debug kernel aarch64
TODO: GDB fails with:
@@ -2695,7 +2696,7 @@ I've also tried the fix at: https://stackoverflow.com/questions/27411621/remote-
but it did not help.
=== gem5 GDB step debug userland processes
==== gem5 GDB step debug userland process
We are unable to use `gdbserver` because of networking: <<gem5-host-to-guest-networking>>