From owner-freebsd-current@FreeBSD.ORG Sat Oct 30 13:06:26 2004 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 1BF5216A4CE for ; Sat, 30 Oct 2004 13:06:26 +0000 (GMT) Received: from node15.coopprint.com (node15.cooperativeprinting.com [208.4.77.15]) by mx1.FreeBSD.org (Postfix) with SMTP id 4C47243D5E for ; Sat, 30 Oct 2004 13:06:25 +0000 (GMT) (envelope-from ryans@gamersimpact.com) Received: (qmail 21555 invoked by uid 0); 30 Oct 2004 13:04:56 -0000 Received: from unknown (HELO ?192.168.0.5?) (63.231.165.87) by node15.coopprint.com with SMTP; 30 Oct 2004 13:04:56 -0000 Message-ID: <418391D5.1070708@gamersimpact.com> Date: Sat, 30 Oct 2004 08:06:29 -0500 From: Ryan Sommers User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Greg 'groggy' Lehey References: <20041030095531.GD2730@eucla.lemis.com> In-Reply-To: <20041030095531.GD2730@eucla.lemis.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: FreeBSD current users Subject: Re: Remote gdb broken in -CURRENT? 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: Sat, 30 Oct 2004 13:06:26 -0000 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