diff options
| author | Tom de Vries <tdevries@suse.de> | 2019-08-22 16:54:59 +0200 |
|---|---|---|
| committer | Tom de Vries <tdevries@suse.de> | 2019-08-22 16:54:59 +0200 |
| commit | 395fad095c9cbc5a8b10557443da981cc3f61885 (patch) | |
| tree | b0f4c779b235d242205a446128101531ee9a4ab5 /gdb/testsuite/gdb.multi | |
| parent | 0535e5d74d6164c49473fe0ce89213aa2b6270b8 (diff) | |
| download | binutils-395fad095c9cbc5a8b10557443da981cc3f61885.zip binutils-395fad095c9cbc5a8b10557443da981cc3f61885.tar.gz binutils-395fad095c9cbc5a8b10557443da981cc3f61885.tar.bz2 | |
[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.
Diffstat (limited to 'gdb/testsuite/gdb.multi')
| -rw-r--r-- | gdb/testsuite/gdb.multi/multi-term-settings.exp | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/gdb/testsuite/gdb.multi/multi-term-settings.exp b/gdb/testsuite/gdb.multi/multi-term-settings.exp index fd3883b..1c550aa 100644 --- a/gdb/testsuite/gdb.multi/multi-term-settings.exp +++ b/gdb/testsuite/gdb.multi/multi-term-settings.exp @@ -212,9 +212,9 @@ proc coretest {inf1_how inf2_how} { send_gdb "\003" if {$expect_ttou} { - gdb_test "" "Quit" "stop with control-c" + gdb_test "" "Quit" "stop with control-c (Quit)" } else { - gdb_test "" "received signal SIGINT.*" "stop with control-c" + gdb_test "" "received signal SIGINT.*" "stop with control-c (SIGINT)" } # Useful for debugging in case the Ctrl-C above fails. |