With gdb.base/break-interp.exp and check-read1, we run get:
...
FAIL: gdb.base/break-interp.exp: LDprelinkNOdebugNO: \
BINprelinkNOdebugNOpieNO: symbol-less: info files (timeout)
FAIL: gdb.base/break-interp.exp: LDprelinkNOdebugNO: \
BINprelinkNOdebugNOpieYES: symbol-less: info files (timeout)
FAIL: gdb.base/break-interp.exp: LDprelinkNOdebugIN: \
BINprelinkNOdebugNOpieNO: symbol-less: info files (timeout)
FAIL: gdb.base/break-interp.exp: LDprelinkNOdebugIN: \
BINprelinkNOdebugNOpieYES: symbol-less: info files (timeout)
...
Fix this by calling exp_continue after each "info files" line.
Tested on x86_64-linux.
gdb/testsuite/ChangeLog:
2019-08-01 Tom de Vries <tdevries@suse.de>
PR testsuite/24863
* gdb.base/break-interp.exp: Use exp_continue after each "info files"
line.
+2019-08-01 Tom de Vries <tdevries@suse.de>
+
+ PR testsuite/24863
+ * gdb.base/break-interp.exp: Use exp_continue after each "info files"
+ line.
+
2019-08-01 Tom de Vries <tdevries@suse.de>
PR testsuite/24863
# to slow processing of wildcard capturing long output
set test "info files"
set entrynohex ""
+ set info_line [join [list \
+ "\r\n" "\[\t\]" "0x\[0-9af\]+" " - " \
+ "0x\[0-9af\]+" " @ " "0x\[0-9af\]+" \
+ " is " "\[^\r\n\]+"] ""]
gdb_test_multiple $test $test {
-re "\r\n\[\t \]*Entry point:\[\t \]*0x(\[0-9a-f\]+)\r\n" {
set entrynohex $expect_out(1,string)
-re "\r\n$gdb_prompt $" {
pass $test
}
+ -re $info_line {
+ # Avoid timeout with check-read1
+ exp_continue
+ }
}
}
}