From owner-freebsd-current Sun Jun 20 17:24:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (Postfix) with ESMTP id DBEB214F09 for ; Sun, 20 Jun 1999 17:24:02 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id SAA00602; Sun, 20 Jun 1999 18:13:19 -0600 (MDT) Date: Sun, 20 Jun 1999 18:13:19 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199906210013.SAA00602@narnia.plutotech.com> To: Greg Lehey Cc: current@FreeBSD.org Subject: Re: Remote serial gdb--status? X-Newsgroups: pluto.freebsd.current In-Reply-To: <19990618114450.Q9893@freebie.lemis.com> <376AA1E6.F529ED99@softweyr.com> <19990621091742.U6820@freebie.lemis.com> User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19990621091742.U6820@freebie.lemis.com> you wrote: > > In fact, it was all OK. The serial port seems to be flaky. It works > OK at 9600 bps, but drops characters at 38400. I'm still > investigating whether this is hardware or software: it seems to work > fine in normal mode, but when it's in serial debug mode it can often > drop two characters at a time, and there's no overrun indication. It looks like isa/sio.c still won't allow you to set a port as both a low-level console and the gdb port. I could not get remote gdb to work correctly after the sio probe without designating the port for low-level console I/O. Now that I've done that, I can't debug at 115200 any more. 38400 seems to work for me, but that is with only minimal testing. Who broke remote debugging in sio? This is a critical tool we can't afford to have broken... 8-( -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message