Difference between revisions of "Debugging The Linux Kernel Using Gdb"
m |
m |
||
Line 1: | Line 1: | ||
− | = Debugging | + | = Debugging the linux kernels using gdb = |
− | The majority of day to day kernel debugging is done by adding print statements to code by using the famous printk function. People use printk it as it is relatively simple and effective technique to use. | + | The majority of day to day kernel debugging is done by adding print statements to code by using the famous printk function. People use printk it as it is relatively simple and effective and cheap technique to use. |
+ | |||
+ | jtag/qemu | ||
and work most of the time. One reason for using these ancient techniques this can probably be found in the roots of | and work most of the time. One reason for using these ancient techniques this can probably be found in the roots of | ||
the Linux kernel (i386) and the tools available to debug those.On the Embedded side | the Linux kernel (i386) and the tools available to debug those.On the Embedded side | ||
we are better served with hardware assisted tools to debug software. | we are better served with hardware assisted tools to debug software. |
Revision as of 03:56, 25 November 2008
Debugging the linux kernels using gdb
The majority of day to day kernel debugging is done by adding print statements to code by using the famous printk function. People use printk it as it is relatively simple and effective and cheap technique to use.
jtag/qemu
and work most of the time. One reason for using these ancient techniques this can probably be found in the roots of the Linux kernel (i386) and the tools available to debug those.On the Embedded side we are better served with hardware assisted tools to debug software.