From owner-freebsd-current Fri Jan 3 11: 7:51 2003 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 CC3B537B401 for ; Fri, 3 Jan 2003 11:07:50 -0800 (PST) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 4C05E43EA9 for ; Fri, 3 Jan 2003 11:07:46 -0800 (PST) (envelope-from nate@rootlabs.com) Received: (qmail 99199 invoked by uid 1000); 3 Jan 2003 19:07:45 -0000 Date: Fri, 3 Jan 2003 11:07:45 -0800 (PST) From: Nate Lawson To: ryan beasley Cc: freebsd-current@freebsd.org Subject: Re: current/stable remote gdb interoperability In-Reply-To: <20030103151344.GA50346@goddamnbastard.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 3 Jan 2003, ryan beasley wrote: > The serial port on the -CURRENT machine is compiled at 38400. FYI, > jesper == 4.7R-p2 debugging box, and fredrik == 5.0 panic box. This > instance of gdb was compiled from source w/ the patches found in the > devel/gdb52 port. (I don't have room for the ports tree locally.) > > The problem I'm running into is primarily erratic behavior. The trace > trap shown below occurs frequently, and while it's only a minor > annoyance, my main concern is gdb randomly freezing when attempting to > get a backtrace. (Sometimes it'll run to completion, others will hang > between frames.) The bt command causes a lot of serial io and so you are probably running into problems with siointr() not being fast. Try backing down to 9600 and see if that works. I've had a similar problem before. Everything else you are doing seems ok. -Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message