On Fri, 18 Jul 2003 20:21:06 -0500, [EMAIL PROTECTED] wrote: >1) sr m is broken in my version, (Its silent) don't know why. > Hmm ... sr anything is silent (but/and error-free).
Probably sysrq is disabled. Recent versions of kdb automatically enable sysrq when you use the kdb sr command. Another good reason to upgrade to kdb v4.3 (do I detect a trend here?). >2) there's other /proc structures that are human readable and are > interesting to look at during crash, e.g. /proc/pci, some stuff > in /proc/ppc64 If getting that data requires taking locks, then it is not safe for a low level kernel debugger, it can hang the debugger. I go to all sorts of lengths to extract data in kdb without tripping over locks that may already be held.
