[gdb/testsuite] Make gdb_test message more informative in multi-term-settings.exp
authorTom de Vries <tdevries@suse.de>
Thu, 22 Aug 2019 14:54:59 +0000 (16:54 +0200)
committerTom de Vries <tdevries@suse.de>
Thu, 22 Aug 2019 14:54:59 +0000 (16:54 +0200)
commit395fad095c9cbc5a8b10557443da981cc3f61885
treeb0f4c779b235d242205a446128101531ee9a4ab5
parent0535e5d74d6164c49473fe0ce89213aa2b6270b8
[gdb/testsuite] Make gdb_test message more informative in multi-term-settings.exp

This racy fail message, reported in PR24929:
...
FAIL: gdb.multi/multi-term-settings.exp: inf1_how=attach: inf2_how=attach: \
  stop with control-c
...
does not make clear which gdb_test fails here:
...
    if {$expect_ttou} {
       gdb_test "" "Quit" "stop with control-c"
    } else {
       gdb_test "" "received signal SIGINT.*" "stop with control-c"
    }
...

Fix this by making the gdb_test message argument more informative.

Tested on x86_64-linux.

gdb/testsuite/ChangeLog:

2019-08-22  Tom de Vries  <tdevries@suse.de>

* gdb.multi/multi-term-settings.exp (coretest): Make gdb_test messages
more informative.
gdb/testsuite/ChangeLog
gdb/testsuite/gdb.multi/multi-term-settings.exp