From owner-freebsd-current@FreeBSD.ORG Mon Nov 1 02:32:03 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 478BD16A4CF for ; Mon, 1 Nov 2004 02:32:03 +0000 (GMT) Received: from duchess.speedfactory.net (duchess.speedfactory.net [66.23.201.84]) by mx1.FreeBSD.org (Postfix) with SMTP id BE97643D5A for ; Mon, 1 Nov 2004 02:32:02 +0000 (GMT) (envelope-from ups@tree.com) Received: (qmail 13059 invoked by uid 89); 1 Nov 2004 02:32:01 -0000 Received: from duchess.speedfactory.net (66.23.201.84) by duchess.speedfactory.net with SMTP; 1 Nov 2004 02:32:01 -0000 Received: (qmail 13053 invoked by uid 89); 1 Nov 2004 02:32:01 -0000 Received: from unknown (HELO palm.tree.com) (66.23.216.49) by duchess.speedfactory.net with SMTP; 1 Nov 2004 02:32:01 -0000 Received: from [127.0.0.1] (localhost.tree.com [127.0.0.1]) by palm.tree.com (8.12.10/8.12.10) with ESMTP id iA12W15R080757; Sun, 31 Oct 2004 21:32:01 -0500 (EST) (envelope-from ups@tree.com) From: Stephan Uphoff To: "Greg 'groggy' Lehey" In-Reply-To: <20041030095531.GD2730@eucla.lemis.com> References: <20041030095531.GD2730@eucla.lemis.com> Content-Type: text/plain Message-Id: <1099276321.65428.78.camel@palm.tree.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Sun, 31 Oct 2004 21:32:01 -0500 Content-Transfer-Encoding: 7bit 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: Mon, 01 Nov 2004 02:32:03 -0000 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? > > Greg Link dcons directly into the kernel. ( Does not work as a module. I also link in firewire and dcons_crom). Stephan