From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15063 invoked by alias); 29 Mar 2004 18:11:23 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 15043 invoked from network); 29 Mar 2004 18:11:23 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sources.redhat.com with SMTP; 29 Mar 2004 18:11:23 -0000 Received: from drow by nevyn.them.org with local (Exim 4.30 #1 (Debian)) id 1B81EI-0005pz-NN; Mon, 29 Mar 2004 13:11:22 -0500 Date: Mon, 29 Mar 2004 18:11:00 -0000 From: Daniel Jacobowitz To: Jeff Johnston Cc: gdb-patches@sources.redhat.com Subject: Re: [patch] New thread test to exercise Daniel's Patch Message-ID: <20040329181122.GB22039@nevyn.them.org> Mail-Followup-To: Jeff Johnston , gdb-patches@sources.redhat.com References: <4062041F.1010302@redhat.com> <40622BEF.8030403@redhat.com> <20040325043950.GA13188@nevyn.them.org> <20040325163437.GA15238@nevyn.them.org> <40633F75.5010908@redhat.com> <20040326175906.GA21136@nevyn.them.org> <406472FB.4010905@redhat.com> <40649CEE.4070607@redhat.com> <20040326211958.GA31610@nevyn.them.org> <4068658F.2070903@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4068658F.2070903@redhat.com> User-Agent: Mutt/1.5.1i X-SW-Source: 2004-03/txt/msg00724.txt.bz2 On Mon, Mar 29, 2004 at 01:06:07PM -0500, Jeff Johnston wrote: > >>+send_gdb "continue\n" > >>+gdb_expect { > > > > > >Everywhere you're using gdb_expect, please use gdb_test_multiple > >instead. For the "after" tests, you can use gdb_test_multiple with > >"" as the first argument. > > > > I tried this initially but I kept getting "Error: internal buffer is full". > I tried lowering the "after" time which is why it ended up 100 below but > that didn't solve the problem. Any suggestions on how to avoid the > "full_buffer" error. I'm not sure about the regexes, since I'm just pulling this out of the top of my head, but you want something like this: -re "error:.*$gdb_prompt $" { fail "msg" } -re "\\\[New thread \[^\]\]*\\\]\r\n" { exp_continue } -re "\\\[Thread \[^\]\]* exited\\\]\r\n" { exp_continue } That will consume any thread create/delete messages, instead of leaving them in the buffer. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer