This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFA] Handle output after 'Program exited normally' consistently (detect spurious output)
- From: Daniel Jacobowitz <drow at false dot org>
- To: Fred Fish <fnf at specifix dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Mon, 15 May 2006 11:55:27 -0400
- Subject: Re: [RFA] Handle output after 'Program exited normally' consistently (detect spurious output)
- References: <200605110709.11444.fnf@specifix.com> <200605111039.54405.fnf@specifix.com>
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 <fnf@specifix.com>
>
> * 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