8sa1-binutils-gdb/gdb/testsuite/lib
Tom de Vries fe1a5cad30 [gdb/testsuite] Log wait status on process no longer exists error
Proc gdb_test_multiple can run into a process no longer exists error, but when
that happens it shows no details about the process:
...
ERROR: Process no longer exists
...

Fix this by showing the wait status of the process in the log:
...
ERROR: GDB process no longer exists
GDB process exited with wait status 8106 exp8 0 0 CHILDKILLED SIGSEGV \
  {segmentation violation}
...

In order to run the wait commmand we need an explicit pid, so we can't use
any_spawn_id, and duplicate the "-i any_spawn_id eof" pattern for gdb_spawn_id,
and add the wait status logging there.

Build and tested on x86_64-linux.

2018-10-24  Tom de Vries  <tdevries@suse.de>

	* lib/gdb.exp (gdb_test_multiple): Log wait status on process no
	longer exists error.
2018-10-24 16:22:58 +02:00
..
ada.exp
append_gdb_boards_dir.exp
build-piece.exp
cache.exp
cell.exp
cl_util.c
cl_util.h
compile-support.exp C++ compile support 2018-08-29 15:12:24 -07:00
compiler.c
compiler.cc
completion-support.exp
cp-support.exp
d-support.exp
data-structures.exp
dtrace.exp
dwarf.exp
fortran.exp
future.exp
gdb-guile.exp
gdb-python.exp
gdb-utils.exp
gdb.exp [gdb/testsuite] Log wait status on process no longer exists error 2018-10-24 16:22:58 +02:00
gdbserver-support.exp
gen-perf-test.exp
go.exp
memory.exp
mi-support.exp Clean up "Reading symbols" output 2018-10-04 13:40:10 -06:00
objc.exp
opencl_hostapp.c
opencl_kernel.cl
opencl.exp
pascal.exp
pdtrace.in
perftest.exp
prelink-support.exp
prompt.exp
range-stepping-support.exp
read1.c
rust-support.exp
selftest-support.exp
set_unbuffered_mode.c
trace-support.exp Clean up gdb.trace test results on targets not supporting this feature. 2018-10-12 17:56:13 -07:00
unbuffer_output.c