Date: Wed, 1 Sep 2004 10:15:52 -0700 From: John-Mark Gurney <gurney_j@resnet.uoregon.edu> To: Rob Deker <deker@slackdot.org> Cc: freebsd-hackers@freebsd.org Subject: Re: The continued remote debugging saga... Message-ID: <20040901171552.GE29902@funkthat.com> In-Reply-To: <4135ED10.3020505@slackdot.org> References: <4135ED10.3020505@slackdot.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Rob Deker wrote this message on Wed, Sep 01, 2004 at 11:38 -0400:
> 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:
If you are able to be at a command line, you could try:
sysctl debug.kdb.current=ddb
> 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 :)
you could also try:
call reset
or:
print reset()
--
John-Mark Gurney Voice: +1 415 225 5579
"All that I will do, has been done, All that I have, has not."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040901171552.GE29902>