>> Is there any method to debug entire kernel from remote machine(remote
> http://www.gcom.com/#linux
(...)
> For instance, one trick that might seem obvious, for code living in
> modules, is to compile -> insmod -> test -> rmmod -> fix -> compile -> ...
> instead of rebooting. It's just that it's not written down anywhere, and
> it's most helpful.
How can you be sure that the module doesn't leave accessed hardware (if it's
a driver) in an unusable state, or, leaves some other rubbish behind?
(This is a genuine question, I don't (yet :) call myself a kernel hacker,
I'm just about able to parse C code for syntax mistakes :)
--
_ciao, Jens_______________________________ http://www.pinguin.conetix.de
cat /dev/boiler/water | tea | sieve > /cup
mount -t hdev /dev/human/mouth01 /mouth ; cat /cup >/mouth/gulp
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/