Hi, Thanks for this nice peace of code.
I just tried the kgdb_light from 2.6.26.1 and activated it by a lilo append "kgdbwait kgdboc=ttyS0,115200". Without any sysreq-g that I also don't understand it worked just by starting "gdb ./vmlinux" on the other machine connected by a rs232-nullmodem-cable. Then I did: "set remotebaud 115200" "target remote /dev/ttyS2" and voila, I'm in. But now, I'm interested in debugging the kernel at a later time out of a running system. In the LinSysSoft-Docu I found a chapter about "Controlling the execution of a kernel" by just hitting "Ctrl+C on the gdb-terminal". But this doesn't work. I can do a "continue" in gdb, but a Ctrl+C doesn't stop and get's me back to single-stepping. How is this done in kgdb_light? regards ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Kgdb-bugreport mailing list Kgdb-bugreport@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport
