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

Update gdbserver.md

Browse Source
This commit is contained in:
Ciro Santilli 六四事件 法轮功 包卓轩
2018-01-16 17:30:22 +00:00
committed by GitHub
parent 04d2d69623
commit 027bca7927
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
gdbserver.md
View File

@@ -76,7 +76,7 @@ QEMU `-gdb` GDB breakpoints are set on virtual addresses, so you can in theory d
- <https://stackoverflow.com/questions/26271901/is-it-possible-to-use-gdb-and-qemu-to-debug-linux-user-space-programs-and-kernel> - <https://stackoverflow.com/questions/26271901/is-it-possible-to-use-gdb-and-qemu-to-debug-linux-user-space-programs-and-kernel>
- <https://stackoverflow.com/questions/16273614/debug-init-on-qemu-using-gdb> - <https://stackoverflow.com/questions/16273614/debug-init-on-qemu-using-gdb>
The only use case I can see for this is to debug the init process (and have fun), otherwise, why wouldn't you just use `gdbserver`? Known of direct userland debugging: The only use case I can see for this is to debug the init process (and have fun), otherwise, why wouldn't you just use `gdbserver`? Known limitations of direct userland debugging:
- the kernel might switch context to another process, and you would enter "garbage" - the kernel might switch context to another process, and you would enter "garbage"