Date: Wed, 09 Feb 2005 09:13:52 +0100 From: Gerald Heinig <gheinig@syskonnect.de> To: Stephan Uphoff <ups@tree.com> Cc: hackers@freebsd.org Subject: Re: Firewire blues Message-ID: <4209C640.3070502@syskonnect.de> In-Reply-To: <1107888844.6309.221.camel@palm.tree.com> References: <420731DD.3050206@syskonnect.de> <1107798981.6309.9.camel@palm.tree.com> <42088232.1030001@syskonnect.de> <4208B9C2.6020007@syskonnect.de> <1107888844.6309.221.camel@palm.tree.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Stephan Uphoff wrote: > There are two ways using kgdb to debug a target with firewire. > The first way basically replaces the slow serial cable for communication > to the remote target gdb stub. > The second way uses the remote DMA capabilities of firewire to directly > read memory of the target WITHOUT using any debugging software/stub on > the target. (Think remote core file) > > Greg Lehey wrote a nice kernel debugging tutorial that explains both > types of firewire debugging. > http://www.lemis.com/grog/Papers/Debug-tutorial/tutorial.pdf > > This should get you started with only minor adjustments (gdb->kgdb) . This is actually the paper I'm using. I've followed the instructions on both methods, but I can't get it to work. The direct machine-machine connection is fine (ie. the one with dconschat). It's the kgdb connection that doesn't work. I presume it worked out of the box for you then? Cheers, Gerald
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4209C640.3070502>