Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: gdb-patches@sourceware.org
Subject: [rfc] Increase match_max size for GDB testsuite?
Date: Thu, 08 Mar 2007 18:39:00 -0000	[thread overview]
Message-ID: <200703081839.l28Id1ok029082@d12av02.megacenter.de.ibm.com> (raw)

Hello,

I'm seeing (somewhat random) failures in callfuncs.exp on spu, which 
appear to be caused by the length of the "info all-registers" output
on the platform.

I'm no dejagnu/expect expert, but seems to me there is a buffer size
that is being set to 20000 in lib/gdb.exp, and if any response from
the inferior exceeds this size, it's not completly predictable what
happens.

Now, since we have 128 registers on the SPU, and each is printed using
a union of 7 different types, the output of "info all-registers" is
quite long, in the range of 50000 bytes.  This exceeds the above limit,
and sometimes causes the test case to fail with
"ERROR: internal buffer is full."

Note that I've seen the same problem in the past with checkpoint.exp
on s390x-ibm-linux (when retrieving the list of 600 checkpoints),
so it doesn't appear to be a spu-only issue.

By simply increasing the "match_max" argument in default_gdb_init,
those failures go away.  I didn't notice any adverse effects either,
so I'd like to make that change -- however, if anybody has a better
solution to the problem, please let me know ...

Bye,
Ulrich



Index: gdb/testsuite/lib/gdb.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/lib/gdb.exp,v
retrieving revision 1.78
diff -c -p -r1.78 gdb.exp
*** gdb/testsuite/lib/gdb.exp	23 Jan 2007 17:11:55 -0000	1.78
--- gdb/testsuite/lib/gdb.exp	8 Mar 2007 18:12:31 -0000
*************** proc default_gdb_init { args } {
*** 1952,1958 ****
      
      # Uh, this is lame. Really, really, really lame. But there's this *one*
      # testcase that will fail in random places if we don't increase this.
!     match_max -d 20000
  
      # We want to add the name of the TCL testcase to the PASS/FAIL messages.
      if { [llength $args] > 0 } {
--- 1952,1958 ----
      
      # Uh, this is lame. Really, really, really lame. But there's this *one*
      # testcase that will fail in random places if we don't increase this.
!     match_max -d 100000
  
      # We want to add the name of the TCL testcase to the PASS/FAIL messages.
      if { [llength $args] > 0 } {
-- 
  Dr. Ulrich Weigand
  GNU Toolchain for Linux on System z and Cell BE
  Ulrich.Weigand@de.ibm.com


             reply	other threads:[~2007-03-08 18:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-08 18:39 Ulrich Weigand [this message]
2007-03-08 18:46 ` Daniel Jacobowitz
2007-03-08 20:01   ` Ulrich Weigand
2007-03-08 20:05     ` Daniel Jacobowitz
2007-03-08 20:10       ` Ulrich Weigand

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=200703081839.l28Id1ok029082@d12av02.megacenter.de.ibm.com \
    --to=uweigand@de.ibm.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