<br><br><div class="gmail_quote">On Wed, Sep 26, 2012 at 5:03 PM, Robert P. J. Day <span dir="ltr"><<a href="mailto:rpjday@crashcourse.ca" target="_blank">rpjday@crashcourse.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
in my online travels yesterday, i ran across this gem, "Linux Kernel<br>
Crash Book":<br>
<br>
<a href="http://www.dedoimedo.com/computers/crash-book.html" target="_blank">http://www.dedoimedo.com/computers/crash-book.html</a><br>
<br>
and am now wondering about what would constitute a reasonable (and<br>
minimal?) list of canonical kernel debugging tools.<br>
<br>
first, while the book above covers Linux Kernel Crash Dump (LKCD),<br>
the author freely admits that it's been pretty much obsoleted by the<br>
more recent and flexible kdump, so there seems to be little value in<br>
digging into LKCD (or, in my case, adding any coverage of it to a<br>
kernel debugging course, which i am currently designing).<br>
<br>
next, someone else's course i'm teaching next week has a kernel<br>
debugging chapter which opens with netdump and diskdump before moving<br>
onto kdump and kexec, but those earlier utilities are *also*<br>
deprecated these days,<br>
<br>
<a href="http://serverfault.com/questions/181554/how-should-i-capture-linux-kernel-panic-stack-traces" target="_blank">http://serverfault.com/questions/181554/how-should-i-capture-linux-kernel-panic-stack-traces</a><br>
<br>
so i would be tempted to skip any coverage of netdump and diskdump in<br>
favour of additional and more advanced coverage of kdump and kexec.<br>
<br>
along those lines, i'm just digging into ftrace and was wondering if<br>
it in any way obsoleted systemtap, but i've heard from more than one<br>
source that while ftrace is allegedly more powerful, systemtap still<br>
has its place and is worth talking about.<br>
<br>
so ... if one was going to put together a (small) toolbox of kernel<br>
debugging tools, what's worth covering? interested in any feedback.<br>
<br>
rday<br>
<br>
--<br>
<br>
========================================================================<br>
Robert P. J. Day Ottawa, Ontario, CANADA<br>
<a href="http://crashcourse.ca" target="_blank">http://crashcourse.ca</a><br>
<br>
Twitter: <a href="http://twitter.com/rpjday" target="_blank">http://twitter.com/rpjday</a><br>
LinkedIn: <a href="http://ca.linkedin.com/in/rpjday" target="_blank">http://ca.linkedin.com/in/rpjday</a><br>
========================================================================<br>
<br>
<br>
<br>
_______________________________________________<br>
Kernelnewbies mailing list<br>
<a href="mailto:Kernelnewbies@kernelnewbies.org">Kernelnewbies@kernelnewbies.org</a><br>
<a href="http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies" target="_blank">http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies</a><br>
</blockquote></div><br>Hi Robert,<br><br>Good to know that you are preparing material. For linux kernel debugging, I would love if you could include, kdb, kgdb and also their setup environment, like now most people do development on Virtual Machine. So the debugger needs to be setup on the VM and its serial port to the host machine, where the debugging logs would be displayed.<br>
<br>- Rohan<br>