Date: Thu, 17 Feb 2005 13:16:44 +1030 From: Greg 'groggy' Lehey <grog@FreeBSD.org> To: Tai-hwa Liang <avatar@mmlab.cse.yzu.edu.tw> Cc: freebsd-current@freebsd.org Subject: Re: gdb over Firewire Message-ID: <20050217024644.GQ69640@wantadilla.lemis.com> In-Reply-To: <050217104048D.63322@www.mmlab.cse.yzu.edu.tw> References: <420C76C3.202@syskonnect.de> <20050217000129.GD69640@wantadilla.lemis.com> <050217104048D.63322@www.mmlab.cse.yzu.edu.tw>
next in thread | previous in thread | raw e-mail | index | archive | help
--sTMGS+9l7rws3PCr Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thursday, 17 February 2005 at 10:43:44 +0800, Tai-hwa Liang wrote: > 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? >> >> >> 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. So you're saying that this approach works for you where it has failed otherwise? Greg -- See complete headers for address and phone numbers. --sTMGS+9l7rws3PCr Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFCFAWUIubykFB6QiMRAgv5AJsEZ9O4DdMND+3gcGzRnnH4g//eYwCfQq6e l2ANDUI+61sClzyF9DA0XHE= =/or8 -----END PGP SIGNATURE----- --sTMGS+9l7rws3PCr--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050217024644.GQ69640>