public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@redhat.com>
To: Diego Novillo <dnovillo@google.com>
Cc: gcc@gnu.org, libstdc++@gcc.gnu.org
Subject: Re: Spurious libstdc++ testsuite failures because of truncated buffered output
Date: Fri, 18 Mar 2011 15:56:00 -0000	[thread overview]
Message-ID: <m37hbws9ry.fsf@redhat.com> (raw)
In-Reply-To: <AANLkTim+0aYi-eYTa6S0HSmyd6HeK_MJ65ALiKsdQtkx@mail.gmail.com>	(Diego Novillo's message of "Fri, 18 Mar 2011 11:04:26 -0400")

Diego Novillo <dnovillo@google.com> writes:

> Is there a way to increase dejagnu's buffering?

expect(1):

       match_max [-d] [-i spawn_id] [size]
             defines the size of the buffer  (in  bytes)  used  internally  by
             expect.  With no size argument, the current size is returned.

             With  the -d flag, the default size is set.  (The initial default
             is 2000.)  With the -i flag, the size is set for the named  spawn
             id, otherwise it is set for the current process.

Andreas.

-- 
Andreas Schwab, schwab@redhat.com
GPG Key fingerprint = D4E8 DBE3 3813 BB5D FA84  5EC7 45C6 250E 6F00 984E
"And now for something completely different."

  parent reply	other threads:[~2011-03-18 15:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-18 15:04 Diego Novillo
2011-03-18 15:30 ` Paolo Carlini
2011-03-18 15:36   ` Diego Novillo
2011-03-18 15:40     ` Paolo Carlini
2011-03-18 15:43       ` Diego Novillo
2011-03-18 16:01     ` Joseph S. Myers
2011-03-18 16:31       ` Diego Novillo
2011-03-18 15:56 ` Andreas Schwab [this message]
2011-03-18 16:27   ` Diego Novillo
2011-03-18 18:05     ` Andreas Schwab
2011-03-18 18:41       ` Diego Novillo

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=m37hbws9ry.fsf@redhat.com \
    --to=schwab@redhat.com \
    --cc=dnovillo@google.com \
    --cc=gcc@gnu.org \
    --cc=libstdc++@gcc.gnu.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).