Date: Sun, 31 Oct 2004 21:32:01 -0500 From: Stephan Uphoff <ups@tree.com> To: "Greg 'groggy' Lehey" <grog@FreeBSD.org> Cc: FreeBSD current users <FreeBSD-current@FreeBSD.org> Subject: Re: Remote gdb broken in -CURRENT? Message-ID: <1099276321.65428.78.camel@palm.tree.com> In-Reply-To: <20041030095531.GD2730@eucla.lemis.com> References: <20041030095531.GD2730@eucla.lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1099276321.65428.78.camel>