From: "Maciej W. Rozycki" <macro@codesourcery.com>
To: <gdb-patches@sourceware.org>
Subject: [PATCH] GDB/testsuite: Bump up `match_max'
Date: Sat, 17 May 2014 20:57:00 -0000 [thread overview]
Message-ID: <alpine.DEB.1.10.1405172136000.12061@tp.orcam.me.uk> (raw)
Hi,
This fixes:
PASS: gdb.base/info-macros.exp: info macro -a -- FOO
ERROR: internal buffer is full.
UNRESOLVED: gdb.base/info-macros.exp: info macros 2
ERROR: internal buffer is full.
UNRESOLVED: gdb.base/info-macros.exp: info macros 3
ERROR: internal buffer is full.
UNRESOLVED: gdb.base/info-macros.exp: info macros 4
FAIL: gdb.base/info-macros.exp: info macros *$pc
ERROR: internal buffer is full.
UNRESOLVED: gdb.base/info-macros.exp: next
FAIL: gdb.base/info-macros.exp: info macros
ERROR: internal buffer is full.
UNRESOLVED: gdb.base/info-macros.exp: next
FAIL: gdb.base/info-macros.exp: info macros 6
ERROR: internal buffer is full.
UNRESOLVED: gdb.base/info-macros.exp: next
FAIL: gdb.base/info-macros.exp: info macros 7
ERROR: internal buffer is full.
UNRESOLVED: gdb.base/info-macros.exp: info macros info-macros.c:42 (PRMS gdb/NNNN)
with the arm-eabi target tested on the i686-mingw32 host where GCC defines
enough macros to exhaust expect's 30000 characters of buffer space.
OK to apply?
2014-05-17 Maciej W. Rozycki <macro@codesourcery.com>
gdb/testsuite/
* lib/gdb.exp (default_gdb_init): Bump `match_max' up from
30000 to 65536.
Maciej
gdb-test-match-max.diff
Index: gdb-fsf-trunk-quilt/gdb/testsuite/lib/gdb.exp
===================================================================
--- gdb-fsf-trunk-quilt.orig/gdb/testsuite/lib/gdb.exp 2014-05-13 02:52:11.347706187 +0100
+++ gdb-fsf-trunk-quilt/gdb/testsuite/lib/gdb.exp 2014-05-17 21:36:38.618201312 +0100
@@ -3539,8 +3539,9 @@ proc default_gdb_init { args } {
# Unlike most tests, we have a small number of tests that generate
# a very large amount of output. We therefore increase the expect
- # buffer size to be able to contain the entire test output.
- match_max -d 30000
+ # buffer size to be able to contain the entire test output. This
+ # is especially needed by gdb.base/info-macros.exp.
+ match_max -d 65536
# Also set this value for the currently running GDB.
match_max [match_max -d]
next reply other threads:[~2014-05-17 20:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-17 20:57 Maciej W. Rozycki [this message]
2014-05-19 14:18 ` Tom Tromey
2014-05-19 14:23 ` Joel Brobecker
2014-05-19 14:37 ` Joel Brobecker
2014-05-19 21:22 ` Doug Evans
2014-05-20 0:47 ` Maciej W. Rozycki
2014-05-20 2:05 ` Joel Brobecker
2014-05-21 19:41 ` Maciej W. Rozycki
2023-10-03 19:53 [PATCH] gdb/testsuite: Bump up 'match_max' Thiago Jung Bauermann
2023-10-04 1:04 ` Simon Marchi
2023-10-04 22:43 ` Thiago Jung Bauermann
2023-10-05 1:39 ` Simon Marchi
2023-10-05 2:41 ` Thiago Jung Bauermann
2023-10-06 17:01 ` Andrew Burgess
2023-10-06 20:34 ` Thiago Jung Bauermann
2023-10-09 9:49 ` Andrew Burgess
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.1.10.1405172136000.12061@tp.orcam.me.uk \
--to=macro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).