* [committed][gdb/testsuite] Fix internal buffer full error in gdb.fortran/module.exp
@ 2020-03-12 12:52 Tom de Vries
0 siblings, 0 replies; only message in thread
From: Tom de Vries @ 2020-03-12 12:52 UTC (permalink / raw)
To: gdb-patches
Hi,
With test-case gdb.fortran/module.exp, I run into:
...
PASS: gdb.fortran/module.exp: fully qualified name of DW_TAG_constant
ERROR: internal buffer is full.
UNRESOLVED: gdb.fortran/module.exp: info variables -n
...
Fix this by using exp_continue while matching the output of "info variable
-n".
Tested on x86_64-linux, using make targets check and check-read1.
Committed to trunk.
Thanks,
- Tom
[gdb/testsuite] Fix internal buffer full error in gdb.fortran/module.exp
gdb/testsuite/ChangeLog:
2020-03-12 Tom de Vries <tdevries@suse.de>
* gdb.fortran/module.exp: Use exp_continue during matching of output
of "info variable -n".
---
gdb/testsuite/gdb.fortran/module.exp | 37 +++++++++++++++++++++++++++---------
1 file changed, 28 insertions(+), 9 deletions(-)
diff --git a/gdb/testsuite/gdb.fortran/module.exp b/gdb/testsuite/gdb.fortran/module.exp
index 6551f5b2cf..1c269e2fed 100644
--- a/gdb/testsuite/gdb.fortran/module.exp
+++ b/gdb/testsuite/gdb.fortran/module.exp
@@ -37,11 +37,8 @@ if ![runto MAIN__] then {
set int_type [fortran_int4]
# Test 'info variables' can find module variables.
-gdb_test "info variables -n" \
+set mod_re \
[multi_line \
- "All defined variables:" \
- "" \
- "File .*$srcfile:" \
"18:\[ \t\]+${int_type} mod1::var_const;" \
"17:\[ \t\]+${int_type} mod1::var_i;" \
"23:\[ \t\]+${int_type} mod2::var_i;" \
@@ -53,11 +50,33 @@ gdb_test "info variables -n" \
"33:\[ \t\]+${int_type} modmany::var_c;" \
"33:\[ \t\]+${int_type} modmany::var_i;" \
"37:\[ \t\]+${int_type} moduse::var_x;" \
- "37:\[ \t\]+${int_type} moduse::var_y;(" \
- "" \
- "File .*:(" \
- "$decimal:.*)+)*"]
-
+ "37:\[ \t\]+${int_type} moduse::var_y;"]
+
+set state 0
+gdb_test_multiple "info variables -n" "" {
+ -re "\r\nAll defined variables:" {
+ if { $state == 0 } { set state 1 }
+ exp_continue
+ }
+ -re "\r\n\r\nFile .*[string_to_regexp $srcfile]:" {
+ if { $state == 1 } { set state 2 }
+ exp_continue
+ }
+ -re $mod_re {
+ if { $state == 2 } { set state 3 }
+ exp_continue
+ }
+ -re "\r\n\r\nFile \[^\r\n\]*:" {
+ exp_continue
+ }
+ -re -wrap "" {
+ if { $state == 3} {
+ pass $gdb_test_name
+ } else {
+ fail $gdb_test_name
+ }
+ }
+}
# Do not use simple single-letter names as GDB would pick up for expectedly
# nonexisting symbols some static variables from system libraries debuginfos.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2020-03-12 12:52 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-03-12 12:52 [committed][gdb/testsuite] Fix internal buffer full error in gdb.fortran/module.exp Tom de Vries
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).