Date: Sat, 30 Oct 2004 08:06:29 -0500 From: Ryan Sommers <ryans@gamersimpact.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: <418391D5.1070708@gamersimpact.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
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? > > This is probably caused by you not having any serial ports flagged for GDB. In /boot/device.hints look for the 'hint.sio.X.flags' where X is your serial port. It should be 0x90 for remote GDB debugging. -- Ryan Sommers ryans@gamersimpact.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?418391D5.1070708>