aboutsummaryrefslogtreecommitdiff
path: root/gdb
diff options
context:
space:
mode:
authorTom de Vries <tdevries@suse.de>2022-12-01 07:25:04 +0100
committerTom de Vries <tdevries@suse.de>2022-12-01 07:25:04 +0100
commitf0cb4aa909d0e3c1c656b2ba9758a59a2cde75de (patch)
treef00538f618ccd0519dee7c8cde1b00ccef86c4a2 /gdb
parent32a5aa2625686a709b22db19300a578d96285dd1 (diff)
downloadgdb-f0cb4aa909d0e3c1c656b2ba9758a59a2cde75de.zip
gdb-f0cb4aa909d0e3c1c656b2ba9758a59a2cde75de.tar.gz
gdb-f0cb4aa909d0e3c1c656b2ba9758a59a2cde75de.tar.bz2
[gdb/testsuite] Wait longer for core generation
When I run the gdb testsuite on a powerpc64le-linux system with (slow) nfs file system, I run into timeouts due to core generation, like for instance: ... (gdb) gcore $outputs/gdb.ada/task_switch_in_core/crash.gcore^M FAIL: gdb.ada/task_switch_in_core.exp: save a corefile (timeout) ... Fix this by using with_timeout_factor 3 in gdb_gcore_cmd. Tested on powerpc64le-linux. Approved-By: Tom Tromey <tom@tromey.com>
Diffstat (limited to 'gdb')
-rw-r--r--gdb/testsuite/lib/gdb.exp20
1 files changed, 13 insertions, 7 deletions
diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp
index 23e3cc0..f41fc13 100644
--- a/gdb/testsuite/lib/gdb.exp
+++ b/gdb/testsuite/lib/gdb.exp
@@ -5730,13 +5730,19 @@ proc gdb_gcore_cmd {core test} {
global gdb_prompt
set result 0
- gdb_test_multiple "gcore $core" $test {
- -re "Saved corefile .*\[\r\n\]+$gdb_prompt $" {
- pass $test
- set result 1
- }
- -re "(?:Can't create a corefile|Target does not support core file generation\\.)\[\r\n\]+$gdb_prompt $" {
- unsupported $test
+
+ set re_unsupported \
+ "(?:Can't create a corefile|Target does not support core file generation\\.)"
+
+ with_timeout_factor 3 {
+ gdb_test_multiple "gcore $core" $test {
+ -re -wrap "Saved corefile .*" {
+ pass $test
+ set result 1
+ }
+ -re -wrap $re_unsupported {
+ unsupported $test
+ }
}
}