From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA/testsuite] Increase expect buffer size (related to GPLv3)
Date: Thu, 23 Aug 2007 20:08:00 -0000 [thread overview]
Message-ID: <20070823200754.GA10856@caradoc.them.org> (raw)
In-Reply-To: <20070823195624.GC6056@adacore.com>
On Thu, Aug 23, 2007 at 03:56:24PM -0400, Joel Brobecker wrote:
> Hello,
>
> After switching "info copying/warranty" to GPLv3, the testsuite showed
> one regression (expected), and two ERRORs because of expect buffer
> overflow. The overflow comes from the fact that the GPLv3 terms are
> much longer than the terms in GPLv2.
>
> I think the attached patch is the appropriate change, but perhaps
> there is a way to change the buffer size locally for the test or
> the testcase, instead of expanding it globally for all testcases.
> I really don't think that growing the buffer to 30kb (from 20kb)
> is a big deal, but perhaps it has some effects that I haven't noticed
> (like performance hits)... Hence the RFA rather than committing it
> using the obvious rule.
>
> 2007-08-23 Joel Brobecker <brobecker@adacore.com>
>
> * lib/gdb.exp (default_gdb_init): Increase expect buffer size
> to 30000 (from 20000).
>
> Tested on x86-linux. No regression.
> OK to apply?
This is fine. It is also possible to do locally; instead of a single
gdb_test, use gdb_test_multiple and match other lines of text using
"exp_continue" to keep looking for the prompt. There's some examples
of this already. But bumping up the limit to a nice bounded value is
fine too.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-08-23 20:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-23 19:55 Joel Brobecker
2007-08-23 20:08 ` Daniel Jacobowitz [this message]
2007-08-23 20:12 ` Joel Brobecker
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=20070823200754.GA10856@caradoc.them.org \
--to=drow@false.org \
--cc=brobecker@adacore.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