From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 17 16:46:40 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 819A316A4CE for ; Thu, 17 Feb 2005 16:46:40 +0000 (GMT) Received: from gatekeeper.syskonnect.de (gatekeeper.syskonnect.de [213.144.13.149]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2318C43D39 for ; Thu, 17 Feb 2005 16:46:37 +0000 (GMT) (envelope-from gheinig@syskonnect.de) Received: from syskonnect.de (skd.de [10.9.15.1])j1HGkq91005025; Thu, 17 Feb 2005 17:46:52 +0100 (MET) Received: from syskonnect.de (localhost [127.0.0.1]) by syskonnect.de (8.12.11/8.12.11) with ESMTP id j1HGkYjg008540; Thu, 17 Feb 2005 17:46:35 +0100 (MET) Message-ID: <4214CA41.4010405@syskonnect.de> Date: Thu, 17 Feb 2005 17:45:53 +0100 From: Gerald Heinig User-Agent: Mozilla Thunderbird 0.5 (X11/20040208) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Stephan Uphoff 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> <1108658236.7621.5613.camel@palm.tree.com> In-Reply-To: <1108658236.7621.5613.camel@palm.tree.com> Content-Type: text/plain; charset=us-ascii; format=flowed 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:46:40 -0000 Stephan Uphoff wrote: > 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 .... That makes sense. Are there any macros with which one can get the thread table address, the address of the currently running thread etc etc? I noticed in Greg's paper he makes several .gdbinit files. Does any of that work/exist under 5.3?