Date: Wed, 20 Feb 2002 10:35:17 -0800 From: "George V. Neville-Neil" <gnn@neville-neil.com> To: Julian Elischer <julian@elischer.org> Cc: freebsd-hackers@freebsd.org Subject: Re: Kernel Debugging over the Ethernet? Message-ID: <200202201835.KAA337017@meer.meer.net> In-Reply-To: Message from Julian Elischer <julian@elischer.org> of "Wed, 20 Feb 2002 10:10:54 PST." <Pine.BSF.4.21.0202201010180.63302-100000@InterJet.elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Folks, Thanks for all the helpful hints. Depending on what I find when I look at how DDB/GDB work now I will probably do the following: A) Use UDP/IP as the transport. Reasons: 1) Easy to write a very minimal, outside the stack, IP/UDP layer. 2) Allows debugging through routers, and in test labs. Makes setting up a real test lab much easier. 3) Makes name to address mapping trivial (you give the machine a name in DNS and you can have your client debugger find it easily). B) Make the back end pluggable (if it is not) Reasons: 1) Allows people to write other back ends and use an IP thingy over it. (Think NetROM, JTAG and other embedded systems and board bring up stuff). Now, if someone could point me to the files that implement the serial line debugging in -CURRENT and perhaps tell me the last person who worked on that that would be great. I'm trying not to make this a big deal, but I also want to make sure that what I do is extensible and generally useful. Thanks, George PS I've got Jonathan Lemon talking to me about this stuff independently as well. -- George V. Neville-Neil gnn@neville-neil.com NIC:GN82 "Those who would trade liberty for temporary security deserve neither" - Benjamin Franklin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200202201835.KAA337017>