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

Dangling notext debug ref

Browse Source
This commit is contained in:
Ciro Santilli
2017-10-07 04:35:39 +01:00
parent f69e894034
commit 4768027b9e
1 changed files with 2 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@@ -281,9 +281,9 @@ Also remember that if your init returns, the kernel will panic, there are just t
- run forever in a loop or long sleep
- `poweroff` the machine
### BusyBox init is fine, but networking gets on my nerves
### BusyBox init is fine, but networking timeout gets on my nerves
I know right?
I know, right?
Add this line to `rootfs_post_build_script`:
@@ -331,8 +331,6 @@ And you now control the counting from GDB.
See also: <http://stackoverflow.com/questions/11408041/how-to-debug-the-linux-kernel-with-gdb-and-qemu>
If you are using text mode:
`O=0` is an impossible dream, `O=2` being the default: <https://stackoverflow.com/questions/29151235/how-to-de-optimize-the-linux-kernel-to-and-compile-it-with-o0> So get ready for some weird jumps, and `<value optimized out>` fun. Why, Linux, why.
### Kernel module debugging