i've asked this before (although possibly not on this list, but maybe so) for peoples' opinions on a minimal but comprehensive set of kernel debugging strategies, without getting into tools that are either too similar, or tools that have clearly been superseded by better tools. i'm putting together a short tutorial on this topic, so i wanted to be fairly complete but not repetitive. at the moment, if i had to keep things really short, here's what i'd explain: 1) using plain "gdb" with vmlinux and /proc/kcore to at least *examine* values in a running kernel, 2) kprobes 3) systemtap but i don't know enough about the other tools to know where they'd fit in here. things like LTT, LTTng, the newer kernel markers, etc., so i'm open to opinions on what my list should look like. thanks. rday p.s. it's possible to perhaps include at least a short reference to virtualization here, perhaps UML, but *only* as a reference. actually covering how to use it would be beyond the scope of the tutorial. -- ======================================================================== Robert P. J. Day Linux Consulting, Training and Annoying Kernel Pedantry Waterloo, Ontario, CANADA http://crashcourse.ca ======================================================================== -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
