I believe Linus’s point was that if you have the source code, you can do
more than just single step through code. For example, you can insert your
own probes into the kernel, recompile it, and at least in theory you would
have a much more accurate diagnostic of what’s going on. Instead of single
stepping to see if this or that happens, just add code to the kernel to do
it for you. If I remember correctly, when asked about debugging, he told
someone, “use the source, dude”, and I can see the point. But I’m not
radical about it, using a debugger is often a good idea. But maybe
single-stepping is a bit overrated, I don’t know.
Alberto.
-----Original Message-----
From: Jim Young [mailto:xxxxx@youngendeavors.com]
Sent: Tuesday, December 04, 2001 10:21 PM
To: NT Developers Interest List
Subject: [ntdev] RE: Global variables
See, all you NT driver developers, things could be worse 
Seriously, relying solely on symbolic debuggers to remedy a poorly designed
driver will alway lead to less than desired results. On the other hand…
Jim
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Christine Ames
Sent: Tuesday, December 04, 2001 6:07 PM
To: NT Developers Interest List
Subject: [ntdev] RE: Global variables
-----Original Message-----
From: Maxim S. Shatskih [ mailto:xxxxx@storagecraft.com
mailto:xxxxx ]
> Sent: Tuesday, December 04, 2001 3:29 PM
> BTW, Christine, can you recommend a kernel debugger for Linux?
>
Linux kernel developers are discouraged from using debuggers, however you
can use gdb and kdb.
Debugging techniques (including the use of kdb) are discussed here:
http://www.xml.com/ldd/chapter/book/ch04.html
http:
Note, however, the following quote from the above reference:
“The kdb Kernel Debugger
Many readers may be wondering why the kernel does not have any more advanced
debugging features built into it. The answer, quite simply, is that Linus
does not believe in interactive debuggers. He fears that they lead to poor
fixes, those which patch up symptoms rather than addressing the real cause
of problems. Thus, no built-in debuggers.
Other kernel developers, however, see an occasional use for interactive
debugging tools. One such tool is the kdb built-in kernel debugger,
available as a nonofficial patch from oss.sgi.com. To use kdb, you must
obtain the patch (be sure to get a version that matches your kernel
version), apply it, and rebuild and reinstall the kernel. Note that, as of
this writing, kdb works only on IA-32 (x86) systems (though a version for
the IA-64 existed for a while in the mainline kernel source before being
removed).”
Harmony,
Christine
—
You are currently subscribed to ntdev as: xxxxx@youngendeavors.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
—
You are currently subscribed to ntdev as: xxxxx@compuware.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
—
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com</http:></mailto:xxxxx>