This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PING] [PATCH] Fix gdb.fortran/array-element.exp failures.
- From: Joel Brobecker <brobecker at adacore dot com>
- To: Gabriel Krisman Bertazi <gabriel at krisman dot be>
- Cc: gdb-patches at sourceware dot org
- Date: Tue, 9 Sep 2014 08:45:31 -0700
- Subject: Re: [PING] [PATCH] Fix gdb.fortran/array-element.exp failures.
- Authentication-results: sourceware.org; auth=none
- References: <m3iondcf2h dot fsf at redhat dot com> <87zjgobth0 dot fsf at Argo dot krisman dot be> <m3pphk9f53 dot fsf at redhat dot com> <8761jbbu6l dot fsf at Argo dot krisman dot be> <m3bnt28g3s dot fsf at redhat dot com> <87lhrv36pm dot fsf at Argo dot krisman dot be> <87zjf3sqrd dot fsf at krisman dot be> <87r4048546 dot fsf_-_ at krisman dot be> <20140909130901 dot GG28404 at adacore dot com> <87d2b4c07h dot fsf at anubis dot Home>
> Sorry I didn't resend the original message with my pings. Here it goes.
>
> This fixes two FAIL results when running this test file due to a
> misplaced "continue" command, which caused the inferior to end execution
> prematurely.
>
> On trunk, we have:
>
> FAIL: gdb.fortran/array-element.exp: continue to breakpoint once again
> (the program exited)
> FAIL: gdb.fortran/array-element.exp: print the second element of array a
>
> === gdb Summary ===
>
> # of expected passes 3
> # of unexpected failures 2
>
> And now, we get:
> === gdb Summary ===
> # of expected passes 3
>
> Is this ok?
The problem is that this does not tell me what was wrong. Just that
some tests did not pass. Although your change seems OK at first glance,
I'd like to do know what it was that did not match, and why it's OK
stop trying to match it now.
--
Joel