From owner-freebsd-hackers@FreeBSD.ORG  Wed Sep 29 19:50:43 2004
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 17B8A16A4CE
	for <hackers@freebsd.org>; Wed, 29 Sep 2004 19:50:43 +0000 (GMT)
Received: from mailserv1.neuroflux.com (mailserv1.neuroflux.com
	[204.228.228.92])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 91ED643D4C
	for <hackers@freebsd.org>; Wed, 29 Sep 2004 19:50:42 +0000 (GMT)
	(envelope-from ryans@gamersimpact.com)
Received: (qmail 4979 invoked by uid 89); 29 Sep 2004 19:57:39 -0000
Received: from unknown (HELO www2.neuroflux.com) (127.0.0.1)
  by localhost with SMTP; 29 Sep 2004 19:57:39 -0000
Received: from 208.4.77.15
        (SquirrelMail authenticated user ryans@gamersimpact.com);
        by www2.neuroflux.com with HTTP;
        Wed, 29 Sep 2004 13:57:39 -0600 (MDT)
Message-ID: <57735.208.4.77.15.1096487859.squirrel@208.4.77.15>
Date: Wed, 29 Sep 2004 13:57:39 -0600 (MDT)
From: "Ryan Sommers" <ryans@gamersimpact.com>
To: hackers@freebsd.org
User-Agent: SquirrelMail/1.4.3a
X-Mailer: SquirrelMail/1.4.3a
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Subject: Serial Console / GDB Port
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Sep 2004 19:50:43 -0000

Is it possible to use the same serial line as the console and GDB port? I
currently have console=comconsole in my loader.conf and am able to break
to the debugger in tip. (I'm Ssh'ing into a box connected via serial line
to the dev box.) I tried setting up gdb on that serial link. Broke into
the debugger in one screen, opened gdb -k kernel.debug in another screen,
when I typed in the target remote /dev/cuaa0 line in gdb though the
garbage printed onto the serial line (beginning of the gdb protocol
session I'm assuming) ended up crashing ddb and panicing the kernel and
I'm unable to access the box over the serial line (and currently don't
have physical access to the box).

Now, I don't think I added the 0x80 flag onto the serial port. Will adding
that flag fix this? Or is there something more I need to do to be able to
enable gdb and a console on the same serial line?


-- 
Ryan Sommers
ryans@gamersimpact.com