From owner-freebsd-current@FreeBSD.ORG Wed Nov 3 08:59:11 2004 Return-Path: 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 8D34216A4CE for ; Wed, 3 Nov 2004 08:59:11 +0000 (GMT) Received: from blackwater.lemis.com (wantadilla.lemis.com [192.109.197.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0FF0543D49 for ; Wed, 3 Nov 2004 08:59:10 +0000 (GMT) (envelope-from grog@lemis.com) Received: from blackwater.lemis.com (wantadilla.lemis.com [192.109.197.135]) by blackwater.lemis.com (Postfix) with ESMTP id B33548560A; Wed, 3 Nov 2004 19:29:06 +1030 (CST) Received: by blackwater.lemis.com (Postfix, from userid 1004) id 947FF4AC37; Wed, 3 Nov 2004 09:58:52 +0100 (CET) Date: Wed, 3 Nov 2004 09:58:52 +0100 From: Greg 'groggy' Lehey To: Stephan Uphoff Message-ID: <20041103085852.GA1199@eucla.lemis.com> References: <20041030095531.GD2730@eucla.lemis.com> <1099276321.65428.78.camel@palm.tree.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1099276321.65428.78.camel@palm.tree.com> User-Agent: Mutt/1.4.2.1i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 cc: FreeBSD current users Subject: Re: Remote gdb broken in -CURRENT? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Nov 2004 08:59:11 -0000 On Sunday, 31 October 2004 at 21:32:01 -0500, Stephan Uphoff wrote: > On Sat, 2004-10-30 at 05:55, Greg 'groggy' Lehey wrote: >> Is anybody currently using remote gdb kernel debugging in -CURRENT? I >> tried yesterday (embarrassingly, during my kernel debug tutorial), and >> it looks as if things are broken. >> >> Specifically, I was doing it in conjunction with firewire. The kernel >> was built with 'options GDB', and it showed that the corresponding gdb >> functions were included, but the sysctl debug.kdb.available shows only >> ddb. I did a bit of looking around for what might have caused it, but >> wasn't successful. >> >> Any ideas? > > Link dcons directly into the kernel. That's not the problem. dcons works fine. As I said, it's gdb, not firewire. > ( Does not work as a module. I also link in firewire and > dcons_crom). I don't know what your problem is, but it's a different one. I'll be home on Monday and will be able to pay more attention to the issue. Greg -- See complete headers for address and phone numbers