From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5508 invoked by alias); 26 Mar 2004 17:30:41 -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 5500 invoked from network); 26 Mar 2004 17:30:40 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sources.redhat.com with SMTP; 26 Mar 2004 17:30:40 -0000 Received: from drow by nevyn.them.org with local (Exim 4.30 #1 (Debian)) id 1B6vAE-00038u-TR; Fri, 26 Mar 2004 12:30:38 -0500 Date: Mon, 29 Mar 2004 16:27:00 -0000 From: Daniel Jacobowitz To: Doug Evans Cc: gdb@sources.redhat.com Subject: Re: commands on tbreak breakpoints, should they work? Message-ID: <20040326173038.GA12047@nevyn.them.org> Mail-Followup-To: Doug Evans , gdb@sources.redhat.com References: <200403261727.i2QHRZU29384@claire.transmeta.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200403261727.i2QHRZU29384@claire.transmeta.com> User-Agent: Mutt/1.5.1i X-SW-Source: 2004-03/txt/msg00277.txt.bz2 On Fri, Mar 26, 2004 at 09:27:35AM -0800, Doug Evans wrote: > gdb = 5.2.1 > > I'm unable to add commands to tbreak breakpoints because gdb first > deletes the breakpoint and then it looks for any breakpoints > with commands to run. > > The docs say > "You can give any breakpoint (or watchpoint or catchpoint) a series of > commands to execute when your program stops due to that breakpoint." > > Is this a gdb bug or doc bug? I'd say gdb bug. Could you try something newer? > > --- > bash$ gcc -g hello.c > bash$ gdb-5.2.1 ./a.out > (gdb) tbreak main > (gdb) commands > echo foo\n > end > (gdb) run > -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer