From: Daniel Jacobowitz <drow@mvista.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: 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:42:00 -0000 [thread overview]
Message-ID: <20020221164225.A27348@nevyn.them.org> (raw)
In-Reply-To: <200202212136.g1LLatO29595@duracef.shout.net>
On Thu, Feb 21, 2002 at 03:36:55PM -0600, Michael Elizabeth Chastain wrote:
> 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'm not arguing that expect/dejagnu version skew hasn't caused problems
in the past, but that's unrelated to this. You don't get the error
because your C library does not contain debug info; no standard
desktop/server distribution leaves it there, generally.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-02-21 21:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-21 13:37 Michael Elizabeth Chastain
2002-02-21 13:42 ` Daniel Jacobowitz [this message]
-- 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=20020221164225.A27348@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@redhat.com \
--cc=mec@shout.net \
/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