From a1a6a5d6fb417238ce4064ef7b3319686f02fd6b Mon Sep 17 00:00:00 2001 From: Ciro Santilli Date: Sun, 25 Mar 2018 19:17:05 +0100 Subject: [PATCH] readme: more uniform titles to gem5 step debug sections --- README.adoc | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/README.adoc b/README.adoc index 14216d0..eb144ec 100644 --- a/README.adoc +++ b/README.adoc @@ -2643,8 +2643,9 @@ Kernel command line: .... [[gem5-gdb]] -=== gem5 GDB step debugging +=== gem5 GDB step debug +==== gem5 GDB step debug kernel Analogous <>, 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: <>