
This is my kernel debugger.  The patches are against .97 pl2, but
are simple enought that adding them to any kernel shouldn't be too
hard.  For documentation you should probably look at the code, although
the built in help function might be enough.  

	You will probably have to do the patches to the top level
makefile by hand, but If anyone planning on using a kernel
debugger should not have any problems with it.

	You should be carefull.  Using the kernel debugger you can
easily corrupt your entire computer.  Filesystems, memory, whatever
can be damaged.

	Press sysrq (alt-sysrq) to activate the debugger.  It will
automatically be activated whenever a trap/general protection error
occurs in kernel mode.  It might also be nice to activate it whenever
a page fault occurs in kernel memory.   Mail comments to

Ross Biro bir7@leland.stanford.edu

Problems:

	I don't think there is anyway to unset a break point except
via the dr7 register.

	It's not very useful without a symbol table handy.  It is
possible to write some user level code which sticks the current
symbol table into the debugger and a debugger function which searches
the table.  This would cause sever kernel bloat, but It might be useful.

	The debugger is very bloated due to the printisn code from gdb.

	It is only a temporary solution until someone with two Linux machines
rights a remote kernel debugger which allows running gdb on one machine
to mess with the kernel on the other.

	