From owner-freebsd-hackers  Thu Mar  7 02:57:52 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id CAA27432
          for hackers-outgoing; Thu, 7 Mar 1996 02:57:52 -0800 (PST)
Received: from time.cdrom.com (time.cdrom.com [192.216.222.226])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id CAA27426
          for <hackers@freebsd.org>; Thu, 7 Mar 1996 02:57:47 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.4/8.6.9) with SMTP id CAA13470; Thu, 7 Mar 1996 02:57:28 -0800 (PST)
To: Greg Lehey <lehey.pad@sni.de>
cc: davidg@Root.COM, hackers@freebsd.org (Hackers; FreeBSD)
Subject: Re: using ddb to debug a double-panic? 
In-reply-to: Your message of "Thu, 07 Mar 1996 11:01:51 +0700."
             <199603071005.LAA20629@nixpbe.pdb.sni.de> 
Date: Thu, 07 Mar 1996 02:57:28 -0800
Message-ID: <13468.826196248@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-hackers@freebsd.org
Precedence: bulk

> I've been thinking about improving ddb.  About 4 years ago, I wrote a
> similar kernel debugger for BSD/386, and was thinking of incorporating
> some of its features into ddb.  One of the things it could do was

I think the real challenge here is to implement gdb-remote.  I was at
Cisco a little while back and got asked this - apparently the Cisco
engineers use the gdb-remote features of their routers to debug IOS
over serial lines.

We could do the same thing with serial console support and a command
in ddb to drop into gdb-remote mode, then you'd just fire up your
gdb on some other box and say "over there!  I want to debug that guy!"

					Jordan