From owner-freebsd-current@FreeBSD.ORG Thu Feb 17 02:43:47 2005 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 3B2A316A4CE; Thu, 17 Feb 2005 02:43:47 +0000 (GMT) Received: from www.mmlab.cse.yzu.edu.tw (www.mmlab.cse.yzu.edu.tw [140.138.150.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id E231443D4C; Thu, 17 Feb 2005 02:43:46 +0000 (GMT) (envelope-from avatar@mmlab.cse.yzu.edu.tw) Received: by www.mmlab.cse.yzu.edu.tw (qmail, from userid 1000) id E04DE4EFDD6; Thu, 17 Feb 2005 10:43:44 +0800 (CST) Received: from localhost (localhost [127.0.0.1]) by www.mmlab.cse.yzu.edu.tw (qmail) with ESMTP id C26A64EFDD5; Thu, 17 Feb 2005 10:43:44 +0800 (CST) Date: Thu, 17 Feb 2005 10:43:44 +0800 (CST) From: Tai-hwa Liang To: Greg 'groggy' Lehey In-Reply-To: <20050217000129.GD69640@wantadilla.lemis.com> Message-ID: <050217104048D.63322@www.mmlab.cse.yzu.edu.tw> References: <420C76C3.202@syskonnect.de> <20050217000129.GD69640@wantadilla.lemis.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: Gerald Heinig cc: freebsd-current@freebsd.org Subject: Re: gdb over Firewire 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, 17 Feb 2005 02:43:47 -0000 On Thu, 17 Feb 2005, Greg 'groggy' Lehey wrote: > On Friday, 11 February 2005 at 10:11:31 +0100, Gerald Heinig wrote: >> Hello Current'ers, >> >> I'm trying to get two-machine kernel debugging over Firewire working, >> unfortunately without much luck so far. dconschat over Firewire works >> fine, but gdb won't attach, complaining about get_tty_state failed, >> among other things. >> Is kernel gdb over Firewire a -current-only feature? > > Sorry for the slow reply; I've been busy. > > No, it's not a current-only feature. It used to work, but I've had a > lot of difficulty since the introduction of the new gdb framework. > > Try this: > > $ sysctl debug.kdb > debug.kdb.available: ddb > debug.kdb.current: ddb > debug.kdb.enter: 0 > debug.kdb.stop_cpus: 1 > > That's what I get, and it indicates that I don't have gdb capability. > If that's what you get, try building a kernel with firewire support > built-in (as opposed to the (recommended) method of loading the > firewire klds later). The background here is the hypothesis that the > kernel checks for debug back-ends at boot time, and not later, so if > you load the firewire klds later, it won't be registered. > Note that this is a hypothesis. If you try this, please let us know > what happens. From my observation, only "device dcons" is necessary to be static linked in kernel, the rest such like firewire.ko and dcons_crom.ko can still be dynamically loaded.