From: Daniel Jacobowitz <drow@mvista.com>
To: Michael Elizabeth Chastain <mec.gnu@mindspring.com>
Cc: gdb@sources.redhat.com, kettenis@chello.nl
Subject: Re: C++ testsuite changes
Date: Thu, 01 Jan 2004 22:19:00 -0000 [thread overview]
Message-ID: <20040101221847.GA13833@nevyn.them.org> (raw)
In-Reply-To: <20040101221545.C2A754B35A@berman.michael-chastain.com>
On Thu, Jan 01, 2004 at 05:15:45PM -0500, Michael Chastain wrote:
> drow> Can you identify what expect feature was causing the problem? I'm
> drow> quite curious.
>
> I'm working on it. Something like this is happening:
>
> virtfunc.exp calls gdb_test_multiple
> gdb_test_multiple gets the "eof" case
> virtfunc.exp calls gdb_test_multiple with nearly the same pattern
> gdb_test_multiple gets the "eof" case
> virtfunc.exp calls gdb_test_multiple with nearly the same pattern
> gdb_test_multiple gets the "eof" case
> virtfunc.exp calls gdb_test_multiple with nearly the same pattern
> gdb_test_multiple gets the "eof" case
> virtfunc.exp calls gdb_test_multiple with a different pattern
> gdb_test_multiple recovers and gets normal output!
>
> I'll try futzing with the problem pattern and see if that makes the
> problem go away.
>
> drow> I suspect we need to do an expect update...
>
> Well, tcl 8.4.5 + expect 5.3.9 + dejagnu 1.4.3 works fine on
> hppa2.0w-hp-hpux11.11 (as well as i686-pc-linux-gnu of course).
>
> What would it take to do an expect update? In particular, what is the
> list of hosts that have to be tested with a new version of 'expect'
> in order to do an expect update?
I haven't the faintest idea. But I think it may be better to simply do
the update and deal with the consequences. The real question is, does
anything other than dejagnu use the in-tree expect?
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-01-01 22:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-01 22:16 Michael Elizabeth Chastain
2004-01-01 22:19 ` Daniel Jacobowitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-01 23:07 Michael Elizabeth Chastain
2004-01-01 22:41 Michael Elizabeth Chastain
2004-01-01 23:02 ` Mark Kettenis
2004-01-01 21:41 Michael Elizabeth Chastain
2004-01-01 21:47 ` Daniel Jacobowitz
2004-01-01 21:23 Michael Elizabeth Chastain
2004-01-01 21:35 ` Daniel Jacobowitz
2004-01-01 20:05 Michael Elizabeth Chastain
2004-01-01 21:08 ` Daniel Jacobowitz
2004-01-01 14:26 Mark Kettenis
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=20040101221847.GA13833@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=kettenis@chello.nl \
--cc=mec.gnu@mindspring.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