diff options
| author | Thiago Jung Bauermann <thiago.bauermann@linaro.org> | 2024-04-04 14:22:22 -0300 |
|---|---|---|
| committer | Thiago Jung Bauermann <thiago.bauermann@linaro.org> | 2024-04-22 13:10:33 -0300 |
| commit | fdaa4939e5024ea809c0d4d1aa6043a60b37d9b5 (patch) | |
| tree | 30cd503485cf157974237fc08a678fa04d9af4c1 | |
| parent | 39f0ac383169d7ef8b3169e483ae95dd185e41bd (diff) | |
| download | gdb-fdaa4939e5024ea809c0d4d1aa6043a60b37d9b5.zip gdb-fdaa4939e5024ea809c0d4d1aa6043a60b37d9b5.tar.gz gdb-fdaa4939e5024ea809c0d4d1aa6043a60b37d9b5.tar.bz2 | |
gdb/testsuite: Use default gdb_expect timeout in runto
runto uses a hard-coded timeout of 30s in its invocation of gdb_expect.
This is normally fine, but for very a slow system (e.g., an emulator) it
may not be enough time for GDB to reach the intended breakpoint.
gdb_expect can obtain a timeout value from user-configurable variables
when it's not given one explicitly, so use that mechanism instead since
the user will have already adjusted the timeout variable to account for
the slow system.
Approved-By: Tom Tromey <tom@tromey.com>
| -rw-r--r-- | gdb/testsuite/lib/gdb.exp | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp index ddee928..cbd37fd 100644 --- a/gdb/testsuite/lib/gdb.exp +++ b/gdb/testsuite/lib/gdb.exp @@ -768,7 +768,7 @@ proc runto { linespec args } { # the "at foo.c:36" output we get with -g. # the "in func" output we get without -g. - gdb_expect 30 { + gdb_expect { -re "(?:Break|Temporary break).* at .*:$decimal.*$gdb_prompt $" { if { $print_pass } { pass $test_name |