From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9119 invoked by alias); 14 Nov 2002 14:58:09 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 9109 invoked from network); 14 Nov 2002 14:58:07 -0000 Received: from unknown (HELO motgate3.mot.com) (144.189.100.103) by sources.redhat.com with SMTP; 14 Nov 2002 14:58:07 -0000 Received: from pobox4.mot.com (pobox4.mot.com [10.64.251.243]) by motgate3.mot.com (Motorola/Motgate3) with ESMTP id gAEEt2UH000071 for ; Thu, 14 Nov 2002 07:55:02 -0700 (MST) Received: [from udc.urbana.css.mot.com (udc.urbana.css.mot.com [192.88.153.21]) by pobox4.mot.com (MOT-pobox4 2.0) with ESMTP id HAA10534 for ; Thu, 14 Nov 2002 07:58:06 -0700 (MST)] Received: from tmclinux.urbana.css.mot.com (tmclinux.urbana.css.mot.com [192.88.153.36]) by udc.urbana.css.mot.com (8.11.6+Sun/8.11.6) with ESMTP id gAEEu6o04786; Thu, 14 Nov 2002 08:56:06 -0600 (CST) X-POPI: The contents of this message are Motorola Internal Use Only (MIUO) unless indicated otherwise in the message. Received: (from tcombs@localhost) by tmclinux.urbana.css.mot.com (8.11.6/8.11.6) id gAEEu6I07058; Thu, 14 Nov 2002 08:56:06 -0600 Date: Thu, 14 Nov 2002 06:58:00 -0000 From: Tim Combs To: James Sampson Cc: GDB Archive Subject: Re: Debugging GDB with GDB Message-ID: <20021114085605.A6694@urbana.css.mot.com> References: <20021114143821.F19325A9BB@postfix3.ofir.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20021114143821.F19325A9BB@postfix3.ofir.com>; from i_am_triumph@ofir.dk on Thu, Nov 14, 2002 at 03:13:07PM +0100 X-SW-Source: 2002-11/txt/msg00167.txt.bz2 The .gdbinit file uses "set prompt (top-gdb)" so you can differentiate between which gdb is running. This works best on the command line as you can readily see which gdb you are in. Things work the same as when you are debugging a program. When you want to stop use ctrl-c and you will see the top-level prompt and you can step through gdb source. When using the command line, I've always found it helpful to open the source file I'm debugging to follow along. Hope this helps Tim On Thu, Nov 14, 2002 at 03:13:07PM +0100, James Sampson wrote: > Hello > > GDB doesn't recognize a COFF file that I have made to a certain target - In > that respect I wish to see whats going on "inside" the GDB, so I'm using GDB > to debug itself - Only thing is, that I don't know how this is done. > I'm using GDB 5.0 to debug GDB 5.2.1, but how do I break or step the GDB when > I have started the GDB being debugged? - The debugged GDB has control of the > console. Is there any way I can use another console for debugging, or is there > another way to do this?. > > Cheers, > > J.S. >