From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 17 16:37:31 2005 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A68FC16A4CE for ; Thu, 17 Feb 2005 16:37:31 +0000 (GMT) Received: from duchess.speedfactory.net (duchess.speedfactory.net [66.23.201.84]) by mx1.FreeBSD.org (Postfix) with SMTP id 1781F43D54 for ; Thu, 17 Feb 2005 16:37:31 +0000 (GMT) (envelope-from ups@tree.com) Received: (qmail 18944 invoked by uid 89); 17 Feb 2005 16:37:28 -0000 Received: from duchess.speedfactory.net (66.23.201.84) by duchess.speedfactory.net with SMTP; 17 Feb 2005 16:37:28 -0000 Received: (qmail 18893 invoked by uid 89); 17 Feb 2005 16:37:28 -0000 Received: from unknown (HELO palm.tree.com) (66.23.216.49) by duchess.speedfactory.net with SMTP; 17 Feb 2005 16:37:28 -0000 Received: from [127.0.0.1] (localhost.tree.com [127.0.0.1]) by palm.tree.com (8.12.10/8.12.10) with ESMTP id j1HGbGw6029887; Thu, 17 Feb 2005 11:37:21 -0500 (EST) (envelope-from ups@tree.com) From: Stephan Uphoff To: Gerald Heinig In-Reply-To: <42133A4F.3020506@syskonnect.de> References: <420731DD.3050206@syskonnect.de> <1107888844.6309.221.camel@palm.tree.com> <420B938D.2040708@syskonnect.de> <1108352789.6309.9948.camel@palm.tree.com> <4213382E.7060603@syskonnect.de> <42133A4F.3020506@syskonnect.de> Content-Type: text/plain Message-Id: <1108658236.7621.5613.camel@palm.tree.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Thu, 17 Feb 2005 11:37:16 -0500 Content-Transfer-Encoding: 7bit cc: Ulrich Spoerlein cc: hackers@freebsd.org Subject: Re: Firewire blues X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Feb 2005 16:37:31 -0000 On Wed, 2005-02-16 at 07:19, Gerald Heinig wrote: > Gerald Heinig wrote: > > Ulrich Spoerlein wrote: > [stuff snipped] > >> > >> Other than that, remote gdb is working. Poking inside the fwmem itself > >> is however not working, I get this after setting eui64_{hi,lo} > >> % kgdb -c /dev/fwmem0.0 kernel.debug > >> ... > >> 0x00000000 in ?? () > > > > > > I got this as well. In my case I assumed it's due to the fact that I > > wasn't using the same kernel file for the debugger as was running on the > > target machine. I didn't investigate further because I can't spend any > > more time on this problem at the moment. > > I'd be interested to know whether that is the problem though. > > I just tried it (had to compile new kernel anyway). It's not due to a > symbol mismatch. > > ENOCLUE :( > With this way of debugging you can only read the memory of the target machine and NOT the state of the CPU. This means that you can not get a current stack backtrace or the current pc. You can however go through the list of processes, find the currently running thread, look at data structures, get backtraces of non-running threads .... Stephan