From owner-freebsd-current  Fri Feb  6 10:06:46 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA22078
          for current-outgoing; Fri, 6 Feb 1998 10:06:46 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.178])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA22073
          for <freebsd-current@freebsd.org>; Fri, 6 Feb 1998 10:06:44 -0800 (PST)
          (envelope-from hasty@rah.star-gate.com)
Received: from rah (localhost.star-gate.com [127.0.0.1])
          by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id KAA10114;
          Fri, 6 Feb 1998 10:06:31 -0800 (PST)
          (envelope-from hasty@rah.star-gate.com)
Message-Id: <199802061806.KAA10114@rah.star-gate.com>
X-Mailer: exmh version 2.0gamma 1/27/96
To: Greg Lehey <grog@lemis.com>
cc: freebsd-current@FreeBSD.ORG, Julian Elischer <julian@whistle.com>
Subject: Re: Remote gdb ? 
In-reply-to: Your message of "Fri, 06 Feb 1998 15:58:59 +1030."
             <19980206155859.02035@freebie.lemis.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 06 Feb 1998 10:06:31 -0800
From: Amancio Hasty <hasty@rah.star-gate.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current"

Nope, gdb remote is broken on -current.

	Cheers,
	Amancio



> On Thu,  5 February 1998 at 20:26:13 -0800, Amancio Hasty wrote:
> >
> > Does anyone know what can cause "Reply contains invalid hex digit 116" ?
> 
> At a guess, it's an overrun.  I haven't been able to get remote gdb to
> work reliably above 9600 bps.  In fact, I haven't been able to get it
> to work reliably at all, but at least at 9600 bps I don't have any
> transmission errors :-)
> 
> Of course, I don't believe it's a hex digit at all.  I'd guess it's
> decimal (0x74 hex, or 't').  Is it repeatable?  From what you show
> below, it appears to be intermittent.
> 
> Greg
> 
> >
> > 	Tnks,
> > 	Amancio
> >
> > (kgdb) set remotebaud 38400
> > (kgdb) target remote /dev/cuaa0
> > Remote debugging using /dev/cuaa0
> > Debugger (msg=0xf01f33eb "manual escape to debugger")
> >     at ../../i386/i386/db_interface.c:319
> > 319     }
> > (kgdb) frame
> > #0  Debugger (msg=0xf01f33eb "manual escape to debugger")
> >     at ../../i386/i386/db_interface.c:319
> > 319     }
> > (kgdb) cont
> > Continuing.
> >
> > Program received signal SIGTRAP, Trace/breakpoint trap.
> > Debugger (msg=0xf0117874 "panic") at ../../i386/i386/db_interface.c:317
> > 317                 in_Debugger = 0;
> > (kgdb) frame
> > #0  Debugger (Ignoring packet error, continuing...
> > msg=Reply contains invalid hex digit 116
> > ) at ../../i386/i386/db_interface.c:317
> > 317                 in_Debugger = 0;
> > (kgdb)
> > {root} stty -f /dev/cuaa0
> > speed 38400 baud;
> > lflags: -icanon -isig -iexten -echo
> > iflags: -icrnl -ixon -ixany -imaxbel -brkint
> > oflags: -opost -onlcr -oxtabs
> > cflags: cs8 -parenb clocal
> > min     time
> > 0       20