Linus> Yes, if you're comparing to a full TCP implementation, plain
Linus> USB serial lines may be simpler (ignoring for the moment the
Linus> fact that there isn't even a standard USB serial line
Linus> protocol, and they may be going the same way as the hardware
Linus> serial lines - the way of the dodo).
Linus> But it should be possible to do a really simple
Linus> UDP-packets-only thing for kgdb. Sure, it may lose packets.
Linus> Tough. Don't debug over a WAN, and try to keep a clean
Linus> direct network connection if you are worried about it. But
Linus> we want kernel printk's to be synchronous anyway, without
Linus> timeouts etc.
Linus> And I suspect you're better off losing packets (very rarely
Linus> over any normal local network) if that means that your
Linus> debugger needs only minimal support. You can always re-type.
I did this a couple of years ago for my research OS (Scout) and it
worked great. It did UDP over Ethernet and was about 300 lines of
code. Rather than using the normal UDP stack, the kernel gdb I/O ran
directly on top of the network driver to reduce the risk of getting
hit by a breakpoint that is in the way of the gdb I/O. The code is
almost too trivial to mention, but for anyone interested, it can still
be found at:
http://www.cs.arizona.edu/scout/software.html
The relevant files are scout/sys/ai/kgdb_net.c and
scout/router/tulip/tulip.c (the latter contains the Ethernet driver
portion).
--david
PS: IIRC, the kgdb protocol has a simple checksumming protocol so it
can deal with packet losses (perhaps not very gracefully, but on a
LAN it's not going to be a problem anyhow).
-
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/