From: Michael Elizabeth Chastain <mec@shout.net>
To: gdb-patches@sources.redhat.com, jimb@redhat.com
Subject: Re: RFA: parse output from `info sources' one filename at a time
Date: Thu, 21 Feb 2002 13:37:00 -0000 [thread overview]
Message-ID: <200202212136.g1LLatO29595@duracef.shout.net> (raw)
Jim Blandy writes:
> This eliminates an `ERROR' when the test is run under Linux. The
> output from `info sources' includes all the shared library source
> files, making it so long that it overflows Expect's buffer.
Interestingly, I don't get any ERROR from gdb.asm/asm-source.exp
on native i686-pc-linux-gnu.
My test script may be different from yours. More likely, my
toolchain may be different from yours. I am using stock tcl 8.3.4,
expect 5.33.0, dejagnu 1.4.2 compiled from source (not whatever
version comes with my Red Hat Linux).
Don't get me wrong, I'm all in favor of the patch. It's good for the
testsuite to be "liberal in what it expects". I just want to note that
there are several different versions of expect and dejagnu in the
world and their differences are materializing in test results.
I have a side project to package up my "standard gnu toolchain"
scripts. They start by downloading 100 megabytes of pristine tarballs
and then build from scratch.
Michael C
next reply other threads:[~2002-02-21 21:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-21 13:37 Michael Elizabeth Chastain [this message]
2002-02-21 13:42 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2002-02-21 23:16 Michael Elizabeth Chastain
2002-02-13 16:10 Jim Blandy
2002-02-21 11:04 ` Michael Snyder
2002-02-21 11:41 ` Fernando Nasser
2002-02-21 12:08 ` Michael Snyder
2002-02-21 12:30 ` Fernando Nasser
2002-02-21 12:58 ` Jim Blandy
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=200202212136.g1LLatO29595@duracef.shout.net \
--to=mec@shout.net \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@redhat.com \
/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