Date: Mon, 25 Mar 1996 07:59:48 -0800 From: "Jordan K. Hubbard" <jkh@time.cdrom.com> To: Greg Lehey <lehey.pad@sni.de> Cc: pst@Shockwave.COM, hackers@freebsd.org, bde@freebsd.org Subject: Re: kgdb / remote gdb of the kernel? Message-ID: <27215.827769588@time.cdrom.com> In-Reply-To: Your message of "Mon, 25 Mar 1996 16:41:37 %2B0700." <199603251544.QAA20457@nixpbe.pdb.sni.de>
next in thread | previous in thread | raw e-mail | index | archive | help
> I don't know of anything involving gdb, but when I was with Tandem > about 5 years ago, they had something similar for the Integrity > series. I'd be interested to know how this worked. > Yes, I had my doubts, too, but at least one manufacturer has managed > it, and the question isn't "is it easy", but rather "is it desirable"? Perhaps, but can we tackle the serial case first? :-) Being able to leverage off of people's existing gdb knowledge would be a real boon - I certainly have the gdb commands pretty much wired into my brain at this point, along with the emacs motion keys.. :-) > stripped-down driver. Note also that the remote debug interface is in > the kernel, and not a user process. Sorry, I phrased that wrong - I'm aware of the degree of separation between debugger and debugee. I simply meant that stepping the kernel past all the code required to deliver an outgoing message packet to the user-mode gdb running elsewhere would be non-trivial. Jordan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?27215.827769588>