|Deletions are marked like this.||Additions are marked like this.|
|Line 26:||Line 26:|
See more: ["http://www.kernelhacking.org/docs/kernelhacking-HOWTO/indexs09.html#oopsanalysis"]
|Line 81:||Line 83:|
|* gdb vmlinux /proc/kcore call gdb with vmlinux(not compressed image of kernel, find it where you did compilation) and optional /proc/kcore - memory of kernel(you must be root)||* gdb vmlinux /proc/kcore call gdb with vmlinux(not compressed image of kernel, in the top level kernel source directory) and optional /proc/kcore - memory of kernel(you must be root)|
|Line 95:||Line 97:|
|== If you want more. ==
see this: ["http://www.kernelhacking.org/docs/kernelhacking-HOWTO/indexs09.html"]
What should I have to fix a bug?
- Bug. Well known particular bug.
- Version of "buged" kernel.
- Bit of luck.
Note: Having a repeatable bug is more then 50% of success.
printk is a very useful function similar to printf(). This function works everywhere and at any time (apart from early stage of booting the kernel when video isn't initialized). It uses log levels to tell the console the importance of each message.
Full list of levels:
KERN_EMERG <-- the most important
KERN_DEBUG <-- the least important
The console will print messages only with a level higher than console_loglevel. By default printk uses DEFAULT_MESSAGE_LOGLEVEL == KERN_WARNING (but this may be changed in the future).
printk() uses a cyclic buffer to manage the messages. Next klogd reads the messages (using /proc/kmsg) from the buffer and gives them to syslogd which writes them to /var/log/messages. (You can configure syslogd by editing /etc/syslog.conf).
An oops is report of a bug in the kernel. When an oops occurs the kernel will print what the registers contain and a "back trace". An oops does not mean the system has crashed, as the system can sometimes recover from the error. If the system can not recover from the error then the kernel will panic and stop running. By default the back trace will contain the addresses of the functions that were called. If you compile your kernel with CONFIG_KALLSYMS=y the oops will be decoded and will display the function names. In the 2.4 kernel you can use ksymoops file_with_oops.txt to see the names of the functions.
Additional compiling options.
These options are very useful when debugging kernel:
Causing errors and printing extra informations.
- Sometimes you will want to see oops informations about some bug. Use BUG() BUG_ON():
- Sometimes you will want to see oops informations and then stop system. Use panic(): if(terrible_error)
- panic("var = %ld \n", var);
- Sometimes you will want to see stack. Use dump_stack():
Magic SysRq Key.
SysRq+b Restart computer
SysRq+e Send SIGTERM to all tasks (with out init !!!)
SysRq+i Send SIGKILL to all tasks (with out init !!!)
SysRq+k Kill all tasks ran from this console
SysRq+l Send SIGTKILL to all tasks (with init !!!)
SysRq+m Dump core and show it on console
SysRq+o Halt system and shutdown it
SysRq+p Print CPU registers on console
SysRq+r Change keyboard from RAW to XLATE
SysRq+s Save dirty buffers on HDD
SysRq+t Show current task info on console
SysRq+u Unmount all filesystems, and remount read only
Note that every user can use SysRq keys, and it can work improperly on an unstable system.
How to use non-exist debugger?
Linus doesn't want a debugger in the kernel because it can lead to fixing symptoms instead of actually understanding the code and fixing the real problem.
However, there are some non-official debuggers (Some require patching the kernel).
Note: use Additional compiling options to make gdb more functional.
gdb (it is not a patch it is GNU debugger)
+ simple to use
- gdb vmlinux /proc/kcore call gdb with vmlinux(not compressed image of kernel, in the top level kernel source directory) and optional /proc/kcore - memory of kernel(you must be root)
- p varaible - show what variable contain
- disassemble name_of_function - disassemble function
- - you can not change variables or other data
kgdb (connect 2 computers, one with kdb and second with gdb)
- +you can change data +all functions of basic gdb are implemented
-you must configure connection
+only one computer needed +all functions of gdb implemented +simple to use
- type "break" in console
starts on oops
If you want more.
When everything fail.
No one likes bugs. So when you spend hours/days on bug fixing, you may write a short and descriptive email containing your all of the information you have found, and send it to LKML. Good luck with Bug Hunting.