From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 1 19:05:29 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2D2A216A4CE for ; Wed, 1 Sep 2004 19:05:29 +0000 (GMT) Received: from itchy.rabson.org (mailgate.nlsystems.com [80.177.232.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id 250D643D31 for ; Wed, 1 Sep 2004 19:05:28 +0000 (GMT) (envelope-from dfr@nlsystems.com) Received: from ns0.nlsystems.com (ns0.nlsystems.com [80.177.232.243]) by itchy.rabson.org (8.12.11/8.12.11) with ESMTP id i81J5IF5020203; Wed, 1 Sep 2004 20:05:18 +0100 (BST) (envelope-from dfr@nlsystems.com) From: Doug Rabson To: freebsd-hackers@freebsd.org, John-Mark Gurney Date: Wed, 1 Sep 2004 20:05:58 +0100 User-Agent: KMail/1.6.2 References: <4135ED10.3020505@slackdot.org> <20040901171552.GE29902@funkthat.com> In-Reply-To: <20040901171552.GE29902@funkthat.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200409012005.58592.dfr@nlsystems.com> X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.64 X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on itchy.rabson.org X-Virus-Scanned: clamd / ClamAV version 0.75.1, clamav-milter version 0.75c on itchy.rabson.org X-Virus-Status: Clean cc: Rob Deker Subject: Re: The continued remote debugging saga... X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Sep 2004 19:05:29 -0000 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.