>
> Hello all,
>
>I would like to get some hints from the experts as to make my way through
>"OOPS" messages from the kernel. I had done some modifications
>to the kernel and as a result I got the problem. But, I was able to debug
>and set right the code by using some printk statements.
>
>What I want to know is to how to use these messages
>as an aid in debugging.
>
> Lastly, I want to know if there is any tool like gdb
> for the kernel debugging and how easy or difficult it is to use.
Check out kgdb on sunsite (pcmcia subdir, version 1.8)
Now if I only could figure out _how_ to use it to debug a module
that OOPses all over the place when I load it.
Hennes
[EMAIL PROTECTED]
kdebug -- a kernel debugging interface for gdb
Kdebug uses gdb's "remote debugging" interface to allow limited
symbolic debugging of a running kernel. Gdb behaves as if it is
passing commands to a remote machine, but in fact, those commands are
executed in the current kernel context.
Key features:
-- Kernel data structures can be read and modified using the usual
gdb commands for manipulating program variables.
-- Kernel functions can be invoked using the gdb "call" command, and
can be used in expressions.
Breakpoints are not supported.
> any suggestions/advice welcome
> Thank you very much for your time.
>
>
> --gopi
>
> -----------------------------------------------------------------
> -
> To unsubscribe from this list: send the line "unsubscribe linux-net" in
> the body of a message to [EMAIL PROTECTED]
>
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
