old-cross-binutils/gdb/testsuite/lib
Pedro Alves 28054d694f gdb_test_multiple: return -1 on internal error
gdb_test_multiple is supposed to return -1 on internal error:

  # Returns:
  #    1 if the test failed, according to a built-in failure pattern
  #    0 if only user-supplied patterns matched
  #   -1 if there was an internal error.

But alas, that's broken, it returns success...  It looks like the code
is assuming an earlier 'set result -1' is still in effect, but
'result' is set to 0 at the end, just before we call gdb_expect:

    set result 0
    set code [catch {gdb_expect $code} string]

gdb/testsuite/
2015-03-02  Pedro Alves  <palves@redhat.com>

	* lib/gdb.exp (gdb_test_multiple) <internal error>: Set result to
	-1.
2015-03-02 20:05:25 +00:00
..
ada.exp
append_gdb_boards_dir.exp
cache.exp
cell.exp
cl_util.c
cl_util.h
compiler.c
compiler.cc
cp-support.exp
d-support.exp
dtrace.exp Simple testsuite for DTrace USDT probes. 2015-02-17 16:41:16 +01:00
dwarf.exp Dwarf assembler: handle one instruction function 2015-02-26 14:21:19 +00:00
fortran.exp
future.exp
gdb-guile.exp
gdb-python.exp
gdb-utils.exp
gdb.exp gdb_test_multiple: return -1 on internal error 2015-03-02 20:05:25 +00:00
gdbserver-support.exp
go.exp
java.exp
mi-support.exp
objc.exp
opencl.exp
opencl_hostapp.c
opencl_kernel.cl
pascal.exp
pdtrace.in Simple testsuite for DTrace USDT probes. 2015-02-17 16:41:16 +01:00
perftest.exp
prelink-support.exp
prompt.exp
range-stepping-support.exp
read1.c
selftest-support.exp
set_unbuffered_mode.c
trace-support.exp
unbuffer_output.c Add "../lib/unbuffer_output.c" and use it in gdb.base/interrupt.c 2015-02-27 13:54:22 +00:00