Date: Wed, 3 Nov 2004 09:58:52 +0100 From: Greg 'groggy' Lehey <grog@FreeBSD.org> To: Stephan Uphoff <ups@tree.com> Cc: FreeBSD current users <FreeBSD-current@FreeBSD.org> Subject: Re: Remote gdb broken in -CURRENT? Message-ID: <20041103085852.GA1199@eucla.lemis.com> In-Reply-To: <1099276321.65428.78.camel@palm.tree.com> References: <20041030095531.GD2730@eucla.lemis.com> <1099276321.65428.78.camel@palm.tree.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041103085852.GA1199>