Date: Thu, 17 Feb 2005 17:45:53 +0100 From: Gerald Heinig <gheinig@syskonnect.de> To: Stephan Uphoff <ups@tree.com> Cc: hackers@freebsd.org Subject: Re: Firewire blues Message-ID: <4214CA41.4010405@syskonnect.de> In-Reply-To: <1108658236.7621.5613.camel@palm.tree.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4214CA41.4010405>