From: Christopher Faylor <me@cgf.cx>
To: gdb@sources.redhat.com
Subject: Re: [Gdb] removing src/dejagnu, src/expect
Date: Tue, 08 Jun 2004 20:57:00 -0000 [thread overview]
Message-ID: <20040608205733.GA7643@coe.casa.cgf.cx> (raw)
In-Reply-To: <20040607215757.4F2554B104@berman.michael-chastain.com>
On Mon, Jun 07, 2004 at 05:57:57PM -0400, Michael Elizabeth Chastain wrote:
>Jim Ingham writes:
>>I just reran the gdb testsuite - on the Apple gdb but this shouldn't
>>make much difference - with the Expect 5.38 from the SourceForge
>>sources, and with Tcl 8.4.4, also from SourceForge, and I didn't see
>>any new failures compared with the expect & tcl from src/.
>
>I've done a similar comparison with the gdb testsuite on native
>i686-pc-linux-gnu, (red hat 8.0, LANG=en_US.UTF-8), and the results
>came out the same. I've been using the released versions of
>tcl+expect+dejagnu for 2.5 years now.
>
>That's just gdb experience though.
>
>I'm okay with shooting first and fixing problems later.
The problem with that approach is that you can't necessarily fix all of
the problems can you? In particular, as you noted in the gcc mailing
list, Cygwin could be a problem. I'm not really looking to take on
new projects right now myself. Maybe someone else will volunteer
to look at this as far as Cygwin is concerned.
cgf
next prev parent reply other threads:[~2004-06-08 20:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-07 21:58 Michael Elizabeth Chastain
2004-06-08 20:57 ` Christopher Faylor [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-09 2:24 Michael Elizabeth Chastain
2004-06-08 21:29 Michael Elizabeth Chastain
2004-06-09 0:54 ` Christopher Faylor
[not found] <1086697608.21986.ezmlm@sources.redhat.com>
2004-06-08 17:35 ` Jim Ingham
[not found] <1086598259.8126.ezmlm@sources.redhat.com>
2004-06-07 21:37 ` Jim Ingham
[not found] <20040605143942.E37E74B104@berman.michael-chastain.com>
2004-06-05 16:13 ` Daniel Jacobowitz
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=20040608205733.GA7643@coe.casa.cgf.cx \
--to=me@cgf.cx \
--cc=gdb@sources.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