Date: Mon, 14 Feb 2005 17:41:30 +0100 From: Gerald Heinig <gheinig@syskonnect.de> To: Stephan Uphoff <ups@tree.com> Cc: hackers@freebsd.org Subject: Re: Firewire blues Message-ID: <4210D4BA.9060109@syskonnect.de> In-Reply-To: <4210CF85.6050902@syskonnect.de> 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> <4209C640.3070502@syskonnect.de> <1107964038.6309.1137.camel@palm.tree.com> <420B938D.2040708@syskonnect.de> <1108352789.6309.9948.camel@palm.tree.com> <4210CF85.6050902@syskonnect.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Gerald Heinig wrote: > Hi Stephan, > > first off, thanks very much for your continuing help on this. It's very > much appreciated. > > I compiled a kernel with exactly the same options that you cited below. > I tried booting it and it stops before the kernel probe routines and > waits for the FireWire GDB connect. > I can't understand how you managed to reboot the target machine without > it entering the debugger and waiting for the remote gdb attach. My > machine refuses to do anything else. > I tried unsetting boot_ddb and boot_gdb in the loader, as well as > clearing the -d and -g flags in the boot_flags variable. No deal, it > still stops and waits for the remote gdb attach. > When I try to attach from the debug machine, gdb complains about > operation not supported. > > Also, I don't understand how your command line > > kgdb -r :5555 -t 11-22-33-44-55... D'oh... What I meant was: kgdb -r :5555 kernel.debug <sigh>. Time to go home I suppose... > > can work. I just get > > ':5555: no such file or directory' > > when I try that. The kgdb manpage also states that it needs a device
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4210D4BA.9060109>