This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
gdb.reverse/until-precsave.exp, timeout on "record save".
- From: Pedro Alves <palves at redhat dot com>
- To: GDB Patches <gdb-patches at sourceware dot org>
- Date: Thu, 02 Feb 2012 17:23:43 +0000
- Subject: gdb.reverse/until-precsave.exp, timeout on "record save".
until-precsave.exp times out while doing a "record save" against the
local extended-remote gdbserver board. "record save" generates a core
file, which just takes longer against a "target *-remote" target than
when running with the native target.
Generating the record log is already covered until a larger timeout
than usual. This just extends the longer timeout region to cover the
core generation as well. Applying in a bit. Tested on x86_64 Fedora 16.
2012-02-02 Pedro Alves <palves@redhat.com>
* gdb.reverse/until-precsave.exp: Also put "record save" under the
extended timeout.
---
gdb/testsuite/gdb.reverse/until-precsave.exp | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/gdb/testsuite/gdb.reverse/until-precsave.exp b/gdb/testsuite/gdb.reverse/until-precsave.exp
index ce62c07..903bbc1 100644
--- a/gdb/testsuite/gdb.reverse/until-precsave.exp
+++ b/gdb/testsuite/gdb.reverse/until-precsave.exp
@@ -52,11 +52,12 @@ gdb_test "break $end_of_main" \
set oldtimeout $timeout
set timeout [expr $oldtimeout + 120]
gdb_test "continue" "Breakpoint .* set breakpoint 10a here .*" "run to end of main"
-set timeout $oldtimeout
+# So can this, against gdbserver, for example.
gdb_test "record save until.precsave" \
"Saved core file until.precsave with execution log\." \
"save process recfile"
+set timeout $oldtimeout
gdb_test "kill" "" "Kill process, prepare to debug log file" \
"Kill the program being debugged\\? \\(y or n\\) " "y"