From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 29 07:14:01 2004 Return-Path: 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 E3A7516A4CE for ; Wed, 29 Sep 2004 07:14:01 +0000 (GMT) Received: from www.citello.it (host170-131.pool80117.interbusiness.it [80.117.131.170]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0202B43D54 for ; Wed, 29 Sep 2004 07:14:01 +0000 (GMT) (envelope-from molter@tin.it) Received: from gattaccio.codalunga (ANice-205-1-10-65.w81-248.abo.wanadoo.fr [81.248.120.65]) by www.citello.it (Postfix) with ESMTP id 2A1D0323; Wed, 29 Sep 2004 09:13:38 +0200 (CEST) Received: by gattaccio.codalunga (Postfix, from userid 1001) id 000A1C10C; Wed, 29 Sep 2004 09:11:58 +0200 (CEST) Date: Wed, 29 Sep 2004 09:11:58 +0200 From: Marco Molteni To: jtoung@arc.nasa.gov Message-Id: <20040929091158.7569f37f.molter@tin.it> In-Reply-To: <200409281622.29556.jtoung@arc.nasa.gov> References: <200409241628.43022.jtoung@earthlink.net> <200409271107.21241.jtoung@arc.nasa.gov> <20040928015212.GN12394@wantadilla.lemis.com> <200409281622.29556.jtoung@arc.nasa.gov> X-Mailer: Sylpheed version 0.9.12 (GTK+ 1.2.10; i386-portbld-freebsd5.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-hackers@freebsd.org Subject: Re: remote debugging question X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Sep 2004 07:14:02 -0000 On Tue, 28 Sep 2004 16:22:29 -0700 Jerry Toung wrote: > Hi Greg, > thank you for all the feedback. The "set remotebaud 1" thing in my > previous email was a typo, I usually enter 9600. > So you're saying that I may have a communication problem. I would like > to point out that I can use "cu -l cuaa0 -s 9600" on both side and all > is well. What do you think could cause this communication issue? I > will run another cvsup soon. May be a bug in 6.0current for kgdb. [..] Note also that you need a -current after 15 sept 2004 to be able to properly set breakpoints and obtain a backtrace without crashing the kernel. (See the commit log for src/sys/i386/i386/gdb_machdep.c for details). marco -- panic("The moon has moved again.");