Date: Wed, 16 Feb 2005 13:19:27 +0100 From: Gerald Heinig <gheinig@syskonnect.de> Cc: Stephan Uphoff <ups@tree.com> Subject: Re: Firewire blues Message-ID: <42133A4F.3020506@syskonnect.de> In-Reply-To: <4213382E.7060603@syskonnect.de> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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 :(
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42133A4F.3020506>