From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14246 invoked by alias); 26 Jul 2002 18:54:08 -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 14057 invoked from network); 26 Jul 2002 18:54:06 -0000 Received: from unknown (HELO takamaka.act-europe.fr) (142.179.108.108) by sources.redhat.com with SMTP; 26 Jul 2002 18:54:06 -0000 Received: by takamaka.act-europe.fr (Postfix, from userid 507) id 814ACD2CBD; Fri, 26 Jul 2002 11:54:06 -0700 (PDT) Date: Fri, 26 Jul 2002 11:54:00 -0000 From: Joel Brobecker To: gdb@sources.redhat.com Subject: "tbreak" and "commands" commands... Message-ID: <20020726185406.GG10000@gnat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i X-SW-Source: 2002-07/txt/msg00285.txt.bz2 Hello, According to the documentation, we should be able to associate a list of commands to execute when the inferior hits a temporary breakpoint. It currently does not seem to be the case. Is there a limitation in this area, or is this a regression (in which case I'll be happy to work on this)? Here is a small copy of a simple session: << GNU gdb 2002-07-26-cvs [snip] This GDB was configured as "i686-pc-linux-gnu"... (gdb) tbreak test.c:8 Breakpoint 1 at 0x804854f: file test.c, line 8. (gdb) command Type commands for when breakpoint 1 is hit, one per line. End with a line saying just "end". >printf "+++ breakpoint hit\n" >continue >end (gdb) run Starting program: /nfs/paris/paris.a/brobecke/act/report/gdb/B726-014__cont_abbrev/test.bonn main () at test.c:8 8 printf ("Hello world.\n"); (gdb) >> As you see, the inferior stopped at breakpoint 1, but the command list was not executed... Thanks, -- Joel