This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: How to abort a test?
- From: Joel Brobecker <brobecker at adacore dot com>
- To: Simon Marchi <simon dot marchi at ericsson dot com>
- Cc: Pedro Alves <palves at redhat dot com>, dejagnu at gnu dot org, gdb-patches <gdb-patches at sourceware dot org>
- Date: Thu, 21 Jan 2016 14:42:14 +0400
- Subject: Re: How to abort a test?
- Authentication-results: sourceware.org; auth=none
- References: <56958359 dot 8070708 at ericsson dot com> <5697CC09 dot 8010306 at redhat dot com> <5697D721 dot 1000305 at ericsson dot com> <5697DABA dot 8010008 at redhat dot com> <5697FA6C dot 7060703 at ericsson dot com> <5697FB9E dot 3080906 at redhat dot com> <56991FB0 dot 5090109 at ericsson dot com> <20160117082709 dot GC4059 at adacore dot com> <569D163D dot 7060609 at ericsson dot com>
> --status does no really impact how a timeout is handled. What happens
> when a timeout occurs in gdb_test is defined by us. Right now, it
> produces a test "fail":
>
> testsuite/lib/gdb.exp:
> 937 timeout {
> 938 if ![string match "" $message] then {
> 939 fail "$message (timeout)"
> 940 }
> 941 set result 1
> 942 }
>
> So you see, for example:
>
> FAIL: gdb.base/break.exp: some test (timeout)
>
> and the test case carries on. A gdb_test timeout is no different than
> a regular fail. If you replace the "fail" at line 939 with "error",
> which throws a TCL exception, then the current test case will abort,
> although in this quite ugly way:
Argh. I was hoping that we would be able to add something at the end
of the timeout handler to abort, but in a nice way.
So, IIUC, without help from dejagnu, there is no way we know of
to abort testcases...
Thanks for having looked into this!
--
Joel