From owner-freebsd-current@FreeBSD.ORG Sun Oct 31 09:27:58 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 72E4D16A4CE for ; Sun, 31 Oct 2004 09:27:58 +0000 (GMT) Received: from blackwater.lemis.com (wantadilla.lemis.com [192.109.197.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F10A43D1D for ; Sun, 31 Oct 2004 09:27:57 +0000 (GMT) (envelope-from grog@lemis.com) Received: from blackwater.lemis.com (wantadilla.lemis.com [192.109.197.135]) by blackwater.lemis.com (Postfix) with ESMTP id F14EA855F6; Sun, 31 Oct 2004 19:57:53 +1030 (CST) Received: by blackwater.lemis.com (Postfix, from userid 1004) id 9E56C4AC41; Sun, 31 Oct 2004 10:27:41 +0100 (CET) Date: Sun, 31 Oct 2004 10:27:41 +0100 From: Greg 'groggy' Lehey To: Ryan Sommers Message-ID: <20041031092741.GE2693@eucla.lemis.com> References: <20041030095531.GD2730@eucla.lemis.com> <418391D5.1070708@gamersimpact.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <418391D5.1070708@gamersimpact.com> User-Agent: Mutt/1.4.2.1i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 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: Sun, 31 Oct 2004 09:27:58 -0000 On Saturday, 30 October 2004 at 8:06:29 -0500, Ryan Sommers wrote: > 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. You shouldn't need any. As I said, this is with firewire. > 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. To select this serial port for both remote gdb and serial console, yes. I did check this and found it to be 0x10 (only serial console). This has not stopped gdb from working on my older -CURRENT (6 months or so) machine. It's possible that you're right, but that would be a recent bug. Unfortunately, we were trying this on the machine of a course participant, and he's no longer available. I'll check your suggestion when I get back home in a week or so. Is anybody currently using remote gdb (serial or firewire) on a -CURRENT built in the last few weeks? If so, did you need to do anything special to get it to run? Greg -- See complete headers for address and phone numbers