From owner-freebsd-current@FreeBSD.ORG Thu Nov 4 16:22:27 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 EE9ED16A4CE; Thu, 4 Nov 2004 16:22:27 +0000 (GMT) Received: from out003.verizon.net (out003pub.verizon.net [206.46.170.103]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6FA3643D39; Thu, 4 Nov 2004 16:22:27 +0000 (GMT) (envelope-from Alex.Kovalenko@verizon.net) Received: from [10.0.3.231] ([138.89.105.63]) by out003.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20041104162226.NNMB3485.out003.verizon.net@[10.0.3.231]>; Thu, 4 Nov 2004 10:22:26 -0600 From: "Alexandre \"Sunny\" Kovalenko" To: Greg 'groggy' Lehey In-Reply-To: <20041103085852.GA1199@eucla.lemis.com> References: <20041030095531.GD2730@eucla.lemis.com> <1099276321.65428.78.camel@palm.tree.com> <20041103085852.GA1199@eucla.lemis.com> Content-Type: text/plain Message-Id: <1099585334.59002.16.camel@RabbitsDen> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Thu, 04 Nov 2004 11:22:14 -0500 Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at out003.verizon.net from [138.89.105.63] at Thu, 4 Nov 2004 10:22:26 -0600 cc: FreeBSD current users cc: Stephan Uphoff 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: Thu, 04 Nov 2004 16:22:28 -0000 On Wed, 2004-11-03 at 03:58, Greg 'groggy' Lehey wrote: > 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. I would side with previous poster -- in my experience, if you have machine with no serial ports, you would have to build firewire and dcons into kernel in order to have GDB listed as output of sysctl debug.kdb.available (and consequently to use remote debugger ;). Prior to doing that, I would see message during the boot saying something to the tune of "No ports available for remote debugging". This was true as of few month ago -- since then I have built firewire/dcons/dcons_crom into the kernel and I've tried it before writing this E-mail on -current as of 10/31 and it seems to work just fine. So, maybe his problem is not that different from yours ;) HTH, Alexandre "Sunny" Kovalenko.