From owner-freebsd-hackers  Mon Mar 25 08:00:56 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id IAA05222
          for hackers-outgoing; Mon, 25 Mar 1996 08:00:56 -0800 (PST)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id IAA05214
          Mon, 25 Mar 1996 08:00:52 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id HAA27217; Mon, 25 Mar 1996 07:59:48 -0800 (PST)
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? 
In-reply-to: Your message of "Mon, 25 Mar 1996 16:41:37 +0700."
             <199603251544.QAA20457@nixpbe.pdb.sni.de> 
Date: Mon, 25 Mar 1996 07:59:48 -0800
Message-ID: <27215.827769588@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> 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