Date: Wed, 01 Sep 2004 11:38:56 -0400 From: Rob Deker <deker@slackdot.org> To: freebsd-hackers@freebsd.org Subject: The continued remote debugging saga... Message-ID: <4135ED10.3020505@slackdot.org>
next in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 So, after a lot of work and help from folks here, I've gotten remote gdb functioning (thanks again to those who helped. In the end there was a bad cable in the mix that was the final screw-up). Now I have one other question/problem. I've got cuaa0 on the target machine as the console, and cuaa1 as the gdb port. In the docs it says that to switch to gdb mode I enter 'gdb' at the ddb prompt. No problem. It also says that typing 'gdb' again will take me back to ddb. What it doesn't say is where to enter it. I've tried in gdb (no success) and on the console (also no success). What am I missing on how to switch back to ddb mode? Alternately, if I can just cause the machine to reset from gdb, that would work. I've tried the following from gdb: ~ > set $eax=0 ~ > jump boot This works SOMETIMES, but for example, the machine is at home and wedged now mid-shutdown (seems I may have screwed up an mbuf pointer and bufdaemon is upset about it). Any suggestions are welcome :) Thanks again, - -d -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBNe0QiaU9aKbHcJcRAn8FAKCUzHq9uLhqtuT48aLCjFq5kXA4UACghqbx GN9A5RK7Ktd9NsFGT5C7t2Q= =ulk7 -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4135ED10.3020505>