From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23104 invoked by alias); 15 May 2006 15:55:35 -0000 Received: (qmail 23071 invoked by uid 22791); 15 May 2006 15:55:33 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Mon, 15 May 2006 15:55:29 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1FffPr-00082w-DV; Mon, 15 May 2006 11:55:27 -0400 Date: Mon, 15 May 2006 15:57:00 -0000 From: Daniel Jacobowitz To: Fred Fish Cc: gdb-patches@sourceware.org Subject: Re: [RFA] Handle output after 'Program exited normally' consistently (detect spurious output) Message-ID: <20060515155527.GC28924@nevyn.them.org> Mail-Followup-To: Fred Fish , gdb-patches@sourceware.org References: <200605110709.11444.fnf@specifix.com> <200605111039.54405.fnf@specifix.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200605111039.54405.fnf@specifix.com> User-Agent: Mutt/1.5.11+cvs20060403 X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2006-05/txt/msg00331.txt.bz2 On Thu, May 11, 2006 at 10:39:54AM -0400, Fred Fish wrote: > On Thursday 11 May 2006 07:09, Fred Fish wrote: > > If we care about testing for cruft between the exit message and the > > gdb prompt, to specifically catch that case, then I think that should > > have it's own dedicated testcase, which I'm happy to write and submit. > > I modified the a2-run.exp test to allow it to run the part of the test that > doesn't require being able to pass arguments, and detect spurious output > after the program exits normally. Patch below. > > -Fred > > 2006-05-11 Fred Fish > > * gdb.base/a2-run.exp: Allow part of test to run when args aren't > required. Check for spurious output after program exits normally. I think this is OK. Does this show up the bug that you were working around elsewhere? -- Daniel Jacobowitz CodeSourcery