aboutsummaryrefslogtreecommitdiff
path: root/gdb/configure.ac
diff options
context:
space:
mode:
authorTom de Vries <tdevries@suse.de>2018-10-24 12:54:33 +0200
committerTom de Vries <tdevries@suse.de>2018-10-24 16:22:58 +0200
commitfe1a5cad302b5535030cdf62895e79512713d738 (patch)
treefb4dbb8491108457c12f9509585621da7899cd95 /gdb/configure.ac
parent8c246a60c08d82066b16973bcd622e671300eb02 (diff)
downloadfsf-binutils-gdb-fe1a5cad302b5535030cdf62895e79512713d738.zip
fsf-binutils-gdb-fe1a5cad302b5535030cdf62895e79512713d738.tar.gz
fsf-binutils-gdb-fe1a5cad302b5535030cdf62895e79512713d738.tar.bz2
[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.
Diffstat (limited to 'gdb/configure.ac')
0 files changed, 0 insertions, 0 deletions