From: "H. J. Lu" <hjl@lucon.org>
To: Joern Rennecke <joern.rennecke@superh.com>
Cc: Jim Ingham <jingham@apple.com>, Aldy Hernandez <aldyh@redhat.com>,
Andreas Tobler <toa@pop.agri.ch>, GCC <gcc@gcc.gnu.org>
Subject: Re: Subject: Kernel bugs that trip expect (Was: Re: 2 new regression on darwin6.1)
Date: Mon, 14 Oct 2002 12:31:00 -0000 [thread overview]
Message-ID: <20021014110015.A30940@lucon.org> (raw)
In-Reply-To: <3DAB04CD.9C674C41@superh.com>; from joern.rennecke@superh.com on Mon, Oct 14, 2002 at 06:54:21PM +0100
On Mon, Oct 14, 2002 at 06:54:21PM +0100, Joern Rennecke wrote:
> Jim Ingham wrote:
> >
> > If you have expect patches have you submitted them back to the expect
> > maintainers? This is now hosted at SourceForge.
> >
> > This won't help gcc & gdb, because they use a weird hacked version of
> > expect - the current expect won't run the testsuite correctly. But if
> > you have found some Linux bug, you should submit a patch to the
> > SourceForge patch tracker...
>
> I had already downloaded & installed the unaltered expect 5.38.0 .
> This has stopped expect from hanging, but the semi-random loss of output
> hasn't improved, if anything, it got worse.
> And no, I haven't got patches, I'm fishing for clues where to start.
>
Try the latest patch from
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=43310
Let me know if it works for you. If it does, I will file a bug report
for expect if it hasn't been fixed already.
H.J.
next prev parent reply other threads:[~2002-10-14 18:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-14 10:34 Joern Rennecke
2002-10-14 10:58 ` H. J. Lu
2002-10-14 11:00 ` Jim Ingham
2002-10-14 11:38 ` Joern Rennecke
2002-10-14 12:31 ` H. J. Lu [this message]
2002-10-15 7:24 ` Joern Rennecke
2002-10-15 7:28 ` H. J. Lu
2002-10-15 10:58 ` H. J. Lu
2002-10-15 13:02 ` Jim Ingham
2002-10-15 13:19 ` H. J. Lu
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=20021014110015.A30940@lucon.org \
--to=hjl@lucon.org \
--cc=aldyh@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=jingham@apple.com \
--cc=joern.rennecke@superh.com \
--cc=toa@pop.agri.ch \
/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).