On Fri, 8 Feb 2002, Pete Zaitcev wrote:
> > You enter <alt>-<sysrq>-n ("nuke"), and then prompts for the pid. It supports
> > backspace and control-U. On serial ports, it retains the same semantics:
> > a break activates this as a sysrq sequence, but if more than 5-seconds pass
> > without any input, it drops out of processing input as a sysrq.
>
> I am afraid we'll have bash and perl in kernel before too long,
> if this avenue is to be pursued.
>
> Why don't you use something like SGI kdb for debugging kernels?
Its very useful to have adequate debugging tools for productions systems.
Something like SGIs kdb is too heavyweight and is not in the mainline
linux kernel and will never, ever get pushed out to any of the production
systems that I work on. However, useful alt-sysrq tools to do post-mortem
analysis of crashed production kernels is something which is extremely
helpful.
What would be *really* useful would be to have crash dump functionality in
the mainline linux kernel. That way you could take a dump and then do
your post-mortem offline with a debugger. Until then I'm all in favor of
throwing bloat into alt-sysrq, since that seems to be Linus' preferred
interface for doing post-mortem analysis.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Feb 15 2002 - 21:00:23 EST