aboutsummaryrefslogtreecommitdiffhomepage
path: root/content/2019-10-27-kernel-debugging-qemu.md
diff options
context:
space:
mode:
Diffstat (limited to 'content/2019-10-27-kernel-debugging-qemu.md')
-rw-r--r--content/2019-10-27-kernel-debugging-qemu.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/content/2019-10-27-kernel-debugging-qemu.md b/content/2019-10-27-kernel-debugging-qemu.md
index 24cc6ee..518b3d5 100644
--- a/content/2019-10-27-kernel-debugging-qemu.md
+++ b/content/2019-10-27-kernel-debugging-qemu.md
@@ -135,7 +135,7 @@ Breakpoint 1, do_execve (filename=0xffff888000060000, __argv=0xffffffff8181e160
## Appendix: Try to get around `<optimized out>`
When debugging the kernel we often face following situation in gdb:
-```text
+```
(gdb) frame
#0 do_execveat_common (fd=fd@entry=-100, filename=0xffff888000120000, argv=argv@entry=..., envp=envp@entry=..., flags=flags@entry=0) at fs/exec.c
@@ -165,7 +165,7 @@ ccflags-y := -Og
After enabling optimize for debug experience `-Og` we can see the following now
in gdb:
-```txt
+```
(gdb) frame
#0 do_execveat_common (fd=fd@entry=-100, filename=0xffff888000120000, argv=argv@entry=..., envp=envp@entry=..., flags=flags@entry=0) at fs/exec.c