From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15233 invoked by alias); 18 Dec 2002 19:01:22 -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 15184 invoked from network); 18 Dec 2002 19:01:14 -0000 Received: from unknown (HELO conn.mc.mpls.visi.com) (208.42.156.2) by 209.249.29.67 with SMTP; 18 Dec 2002 19:01:14 -0000 Received: from grante.comtrol.com (isis.visi.com [209.98.98.8]) by conn.mc.mpls.visi.com (Postfix) with SMTP id 5D37E813C for ; Wed, 18 Dec 2002 13:00:58 -0600 (CST) Received: (qmail 9910 invoked by uid 500); 18 Dec 2002 18:59:21 -0000 Date: Wed, 18 Dec 2002 11:01:00 -0000 From: Grant Edwards To: gdb@sources.redhat.com Subject: Re: Debugging GDB and breaking? Message-ID: <20021218125921.A9829@visi.com> References: <200212181523.gBIFNUZ10382@duracef.shout.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200212181523.gBIFNUZ10382@duracef.shout.net>; from mec@shout.net on Wed, Dec 18, 2002 at 09:23:30AM -0600 X-SW-Source: 2002-12/txt/msg00277.txt.bz2 On Wed, Dec 18, 2002 at 09:23:30AM -0600, Michael Elizabeth Chastain wrote: > Some general hints for debugging gdb: > > I start with "gdb /my/gdb/to/debug/bin/gdb". I like to use a stable gdb > for the top gdb, such as the vendor-supplied gdb or gdb 5.3. Also this > helps separate, in my mind, the top gdb from the inferior gdb. > > Then I immediately: > > (gdb) set prompt [top] > [top] break help_command > [top] set args /program/under/test > > The first line distinguishes the top gdb from the inferior gdb. Running them in separate ttys prevents confusion for me: gdb -tty= /my/buggy/gdb Or I use the equivalent menu item in DDD or Insight... -- Grant Edwards grante@visi.com