From: Brian J. Watson <Brian.J.W<atson@co...> - 2001-09-11 00:24:40
We're thinking of rolling our kdb into the next releases of CI and SSI,
to help with bug reports. At the very least, it's nice to know what the
stack trace was leading up to a NULL or bad pointer dereference.
Our kdb is SGI's kdb, modified to patch cleanly against a SSI kernel,
and enhanced with a call command for calling kernel functions such as
debug print routines. For those who are not comfortable poking around
the innards of a kernel, we would ask that if something goes wrong and a
kdb> prompt pops up, just type bt and hit Enter. If you're running over
a serial console, you could then copy and paste the resulting stack
trace into a mail message. If you're on a physical console, retyping the
whole thing is a bit of a drag. We would just ask that you copy a subset
of the information into a mail message.
Are there any comments, objections, or questions about this?
Brian Watson | "The common people of England... so
Linux Kernel Developer | jealous of their liberty, but like the
Open SSI Clustering Project | common people of most other countries
Compaq Computer Corp | never rightly considering wherein it
Los Angeles, CA | consists..."
| -Adam Smith, Wealth of Nations, 1776