From owner-freebsd-current@FreeBSD.ORG Sun Oct 31 12:55:57 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 2E73916A4CE; Sun, 31 Oct 2004 12:55:57 +0000 (GMT) Received: from www.mmlab.cse.yzu.edu.tw (www.mmlab.cse.yzu.edu.tw [140.138.145.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id B3D9943D5C; Sun, 31 Oct 2004 12:55:56 +0000 (GMT) (envelope-from avatar@mmlab.cse.yzu.edu.tw) Received: by www.mmlab.cse.yzu.edu.tw (qmail, from userid 1000) id 0E08C4EFCD9; Sun, 31 Oct 2004 20:55:51 +0800 (CST) Received: from localhost (localhost [127.0.0.1]) by www.mmlab.cse.yzu.edu.tw (qmail) with ESMTP id 09D0D4EFCD8; Sun, 31 Oct 2004 20:55:51 +0800 (CST) Date: Sun, 31 Oct 2004 20:55:50 +0800 (CST) From: Tai-hwa Liang To: Greg 'groggy' Lehey In-Reply-To: <20041031092741.GE2693@eucla.lemis.com> Message-ID: <041031192208A.54797@www.mmlab.cse.yzu.edu.tw> References: <20041030095531.GD2730@eucla.lemis.com> <418391D5.1070708@gamersimpact.com> <20041031092741.GE2693@eucla.lemis.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: Ryan Sommers 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 12:55:57 -0000 On Sun, 31 Oct 2004, Greg 'groggy' Lehey wrote: > 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? I can't get remote gdb works with firewire since the new KDB framework was imported. If I remembered correctly, someone was asked the similar question about on the list a couple of months ago, and the answer is simply: It's broken, use serial port instead.