Date: Wed, 1 Sep 2004 20:05:58 +0100 From: Doug Rabson <dfr@nlsystems.com> To: freebsd-hackers@freebsd.org, John-Mark Gurney <gurney_j@resnet.uoregon.edu> Cc: Rob Deker <deker@slackdot.org> Subject: Re: The continued remote debugging saga... Message-ID: <200409012005.58592.dfr@nlsystems.com> In-Reply-To: <20040901171552.GE29902@funkthat.com> References: <4135ED10.3020505@slackdot.org> <20040901171552.GE29902@funkthat.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday 01 September 2004 18:15, John-Mark Gurney wrote: > 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 You used to be able to use GDB's detach command to switch back.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200409012005.58592.dfr>