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
_______________________________________________
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
