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. |
||
---|---|---|
.. | ||
base.exp | ||
bkpt-multi-exec.c | ||
bkpt-multi-exec.exp | ||
crashme.c | ||
dummy-frame-restore.c | ||
dummy-frame-restore.exp | ||
goodbye.c | ||
hangout.c | ||
hello.c | ||
info-threads.exp | ||
multi-arch-exec.c | ||
multi-arch-exec.exp | ||
multi-arch.exp | ||
multi-attach.c | ||
multi-attach.exp | ||
multi-term-settings.c | ||
multi-term-settings.exp | ||
remove-inferiors.c | ||
remove-inferiors.exp | ||
tids.c | ||
tids.exp | ||
watchpoint-multi-exit.c | ||
watchpoint-multi-exit.exp | ||
watchpoint-multi.c | ||
watchpoint-multi.exp |