From owner-freebsd-current@FreeBSD.ORG  Mon Sep 29 23:25:01 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id CC8BE16A4B3; Mon, 29 Sep 2003 23:25:01 -0700 (PDT)
Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id B68C04401F; Mon, 29 Sep 2003 23:24:59 -0700 (PDT)
	(envelope-from bde@zeta.org.au)
Received: from gamplex.bde.org (katana.zip.com.au [61.8.7.246])
	by mailman.zeta.org.au (8.9.3p2/8.8.7) with ESMTP id QAA16726;
	Tue, 30 Sep 2003 16:24:57 +1000
Date: Tue, 30 Sep 2003 16:23:35 +1000 (EST)
From: Bruce Evans <bde@zeta.org.au>
X-X-Sender: bde@gamplex.bde.org
To: "Greg 'groggy' Lehey" <grog@FreeBSD.org>
In-Reply-To: <20030929083007.GA33083@wantadilla.lemis.com>
Message-ID: <20030930162115.P3387@gamplex.bde.org>
References: <20030929083007.GA33083@wantadilla.lemis.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: FreeBSD current users <FreeBSD-current@FreeBSD.org>
Subject: Re: Serial debug broken in recent -CURRENT?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Sep 2003 06:25:02 -0000

On Mon, 29 Sep 2003, Greg 'groggy' Lehey wrote:

> After building a new kernel, remote serial gdb no longer works.  When
> I issue a 'continue' command, I lose control of the system, but it
> doesn't continue running.  Has anybody else seen this?

It works as well as it did a few months ago here.  (Not very well compared
with ddb.  E.g., calling a function is usually fatal.)

Bruce