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 02:05:57 +01:00
Code Issues Releases Wiki Activity

run: --trace-insts-stdout

Browse Source
This commit is contained in:
Ciro Santilli 六四事件 法轮功
2019-02-20 00:00:00 +00:00
parent e855a262fd
commit 2b93b18646
2 changed files with 29 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
README.adoc
View File

@@ -3110,7 +3110,7 @@ where `build` builds the whole toolchain for us.
`./run --userland` path resolution is analogous to <<baremetal-setup-getting-started,that of `./run --baremetal`>>.
`./build user-mode-qemu` first builds Buildroot, and then runs `./build-userland`, which is further documented at: <<userland-directory>>.
`./build user-mode-qemu` first builds Buildroot, and then runs `./build-userland`, which is further documented at: <<userland-directory>>. It also builds QEMU.
==== User mode simulation with glibc
@@ -9057,12 +9057,23 @@ Output the trace to stdout instead of a file:
--arch aarch64 \
--emulator gem5 \
--eval 'm5 exit' \
--trace Exec \
--trace ExecAll \
--trace-stdout \
;
....
This would produce a lot of output however, so you will likely not want that when tracing a Linux kernel boot instructions. But it can be very convenient for smaller traces.
We also have a shortcut for `--trace ExecAll -trace-stdout` with `--trace-insts-stdout`
....
./run \
--arch aarch64 \
--emulator gem5 \
--eval 'm5 exit' \
--trace-insts-stdout \
;
....
This would produce a lot of output however, so you will likely not want that when tracing a Linux kernel boot instructions. But it can be very convenient for smaller traces such as <<baremetal>>.
List all available debug flags: