From owner-freebsd-hackers  Thu Apr 24 06:50:02 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id GAA06945
          for hackers-outgoing; Thu, 24 Apr 1997 06:50:02 -0700 (PDT)
Received: from chai.plexuscom.com (chai.plexuscom.com [207.87.46.100])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA06913
          for <hackers@freebsd.org>; Thu, 24 Apr 1997 06:49:59 -0700 (PDT)
Received: from chai.plexuscom.com (localhost [127.0.0.1])
	by chai.plexuscom.com (8.8.5/8.8.5) with ESMTP id JAA13535;
	Thu, 24 Apr 1997 09:51:24 -0400 (EDT)
Message-Id: <199704241351.JAA13535@chai.plexuscom.com>
To: Pavlin Ivanov Radoslavov <pavlin@catarina.usc.edu>
Cc: hackers@freebsd.org
Subject: Re: Kernel remote debugging using gdb 
In-reply-to: Your message of "Thu, 24 Apr 1997 01:40:52 PDT."
             <199704240840.BAA06706@catarina.usc.edu> 
Date: Thu, 24 Apr 1997 09:51:23 -0400
From: Bakul Shah <bakul@torrentnet.com>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

If you can _live_ with sharing the same sio port for console and
gdb, there is a way.  Not pretty but it works.  First, as Amancio
suggested, swap your connections to the UUG (Unix under GDB :-) so
that the PC is now attached to COM1.  Now you can switch between gdb
and a comm program like kermit.  The kermit window will show you
all your printfs.  Any time you want to drop into gdb, send a break,
stop kermit and switch to gdb and hit ^C in it.  If you are in
kermit when the kernel stops due to a breakpoint it is easy to see
and switch to gdb.

I haven't yet tried Bruce's latest sio changes so don't know how
well they solve the problem.