From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 1 17:15:54 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 B6B0316A4CE for ; Wed, 1 Sep 2004 17:15:54 +0000 (GMT) Received: from mail6.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8DABA43D1F for ; Wed, 1 Sep 2004 17:15:54 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: (qmail 19934 invoked from network); 1 Sep 2004 17:15:54 -0000 Received: from gate.funkthat.com (HELO hydrogen.funkthat.com) ([69.17.45.168]) (envelope-sender ) by mail6.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 1 Sep 2004 17:15:54 -0000 Received: from hydrogen.funkthat.com (jqdovs@localhost.funkthat.com [127.0.0.1])i81HFruU081381; Wed, 1 Sep 2004 10:15:53 -0700 (PDT) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.12.10/8.12.10/Submit) id i81HFqvG081380; Wed, 1 Sep 2004 10:15:52 -0700 (PDT) Date: Wed, 1 Sep 2004 10:15:52 -0700 From: John-Mark Gurney To: Rob Deker Message-ID: <20040901171552.GE29902@funkthat.com> Mail-Followup-To: Rob Deker , freebsd-hackers@freebsd.org References: <4135ED10.3020505@slackdot.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4135ED10.3020505@slackdot.org> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 4.2-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html cc: freebsd-hackers@freebsd.org Subject: Re: The continued remote debugging saga... X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: John-Mark Gurney 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 17:15:54 -0000 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."