From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 16 12:20:08 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 D3A0116A4CE for ; Wed, 16 Feb 2005 12:20:08 +0000 (GMT) Received: from gatekeeper.syskonnect.de (gatekeeper.syskonnect.de [213.144.13.149]) by mx1.FreeBSD.org (Postfix) with ESMTP id 249B643D2D for ; Wed, 16 Feb 2005 12:20:08 +0000 (GMT) (envelope-from gheinig@syskonnect.de) Received: from syskonnect.de (skd.de [10.9.15.1])j1GCKN91013817; Wed, 16 Feb 2005 13:20:23 +0100 (MET) Received: from syskonnect.de (localhost [127.0.0.1]) by syskonnect.de (8.12.11/8.12.11) with ESMTP id j1GCK6ZQ003068; Wed, 16 Feb 2005 13:20:06 +0100 (MET) Message-ID: <42133A4F.3020506@syskonnect.de> Date: Wed, 16 Feb 2005 13:19:27 +0100 From: Gerald Heinig User-Agent: Mozilla Thunderbird 0.5 (X11/20040208) X-Accept-Language: en-us, en MIME-Version: 1.0 References: <420731DD.3050206@syskonnect.de> <42088232.1030001@syskonnect.de> <1107888844.6309.221.camel@palm.tree.com> <1107964038.6309.1137.camel@palm.tree.com> <420B938D.2040708@syskonnect.de> <1108352789.6309.9948.camel@palm.tree.com> <20050216110200.GA913@galgenberg.net> <4213382E.7060603@syskonnect.de> In-Reply-To: <4213382E.7060603@syskonnect.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Ulrich Spoerlein cc: hackers@freebsd.org cc: Stephan Uphoff 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: Wed, 16 Feb 2005 12:20:08 -0000 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 :(