diff options
| author | Tom de Vries <tdevries@suse.de> | 2022-04-14 13:52:19 +0200 |
|---|---|---|
| committer | Tom de Vries <tdevries@suse.de> | 2022-04-14 13:52:19 +0200 |
| commit | f48fc32448205963c597975f1bce3db3c86094ad (patch) | |
| tree | ab8ddee62b0f114c55d4fb9d70c956ee53876616 | |
| parent | d4c9e8f5834939909859ad748c31b7a3d239aeab (diff) | |
| download | binutils-gdb-f48fc32448205963c597975f1bce3db3c86094ad.tar.gz | |
[gdb/testsuite] Fix gdb.base/stap-probe.exp with read1
When running test-case gdb.base/stap-probe.exp with make target check-read1, I
run into this and similar:
...
FAIL: gdb.base/stap-probe.exp: without semaphore, not optimized: \
info probes stap (timeout)
...
Fix this by using gdb_test_lines instead of gdb_test.
Tested on x86_64-linux.
| -rw-r--r-- | gdb/testsuite/gdb.base/stap-probe.exp | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/gdb/testsuite/gdb.base/stap-probe.exp b/gdb/testsuite/gdb.base/stap-probe.exp index e86c7897b93..75ad56baff6 100644 --- a/gdb/testsuite/gdb.base/stap-probe.exp +++ b/gdb/testsuite/gdb.base/stap-probe.exp @@ -42,10 +42,10 @@ proc stap_test {exec_name {args ""}} { "check argument not at probe point" if {[string first "-DUSE_SEMAPHORES" $args] != -1} { - gdb_test "info probes stap" \ + gdb_test_lines "info probes stap" "" \ "test *user *$hex *$hex .*" } else { - gdb_test "info probes stap" \ + gdb_test_lines "info probes stap" "" \ "test *user *$hex .*" } |