From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Received: (qmail 24746 invoked from network); 3 Feb 2002 15:18:47 -0000 Received: from unknown (HELO dublin.ACT-Europe.FR) (212.157.227.154) by sources.redhat.com with SMTP; 3 Feb 2002 15:18:47 -0000 Received: from berlin.ACT-Europe.FR (berlin.act-europe.fr [212.157.227.169]) by dublin.ACT-Europe.FR (Postfix) with ESMTP id 15E46229E15; Sun, 3 Feb 2002 16:18:46 +0100 (MET) Received: by berlin.ACT-Europe.FR (Postfix, from userid 507) id AC4AF7B4; Sun, 3 Feb 2002 16:18:45 +0100 (CET) Date: Sun, 03 Feb 2002 12:29:00 -0000 From: Joel Brobecker To: Salman Khilji Cc: gdb@sources.redhat.com Subject: Re: Debugging gdb with gdb Message-ID: <20020203161845.B12617@act-europe.fr> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from salmankhilji@hotmail.com on Fri, Feb 01, 2002 at 04:25:15PM +0000 X-SW-Source: 2002-02/txt/msg00062.txt.bz2 > So the question is: How do I temporarily stop the target application in > gdb---set a break point in the target---then continue? This is useful in > GUI applications as well. FWIW, I debug GDB a bit differently: I start the inferior GDB in a terminal. I then run another GDB, and attach it to the inferior. The idea behind this is that I want to avoid mixing the I/O in the inferior with the commands I'm sending to GDB. For the GUI lovers, GVD facilitates this, because it offers a File->Attach menu, which will then present you with a list of process. Click, click, click, and you're attached... -- Joel