From: Andrew Cagney <ac131313@cygnus.com>
To: Michael Elizabeth Chastain <chastain@cygnus.com>
Cc: msnyder@cygnus.com, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] quoting curly braces in call-rt-st
Date: Thu, 05 Jul 2001 10:11:00 -0000 [thread overview]
Message-ID: <3B44982C.4090005@cygnus.com> (raw)
In-Reply-To: <200107051534.IAA24501@stanley.cygnus.com>
> I think the patterns are breaking now because a different person is
> running them in a different environment -- specifically, with a different
> version of 'expect'. I always use /usr/progressive/bin/expect
> on every platform. I'm not sure what MichaelS is using; it depends
> on his path.
(Brain gets out of first gear...) Yes, if I zap the expect built from
the CVS repository I'm going to get the expect in progressive
(For those wondering what progressive is, it is a Red Hat standardized
tested/built version of GCC+BINUTILS+GDB+...)
> This means our test harness machinery is vulnerable and fragile.
> That's not good. :(
I think it means that expect has a poorly defined regex syntax and now
it is changing under our feet. Once a an expression is defined it
should just keep working.
Andrew
next prev parent reply other threads:[~2001-07-05 10:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-05 8:34 Michael Elizabeth Chastain
2001-07-05 10:11 ` Andrew Cagney [this message]
[not found] <3B411440.1691E1E5@cygnus.com>
2001-07-09 13:37 ` Fernando Nasser
2001-07-09 13:42 ` H . J . Lu
2001-07-09 15:22 ` Fernando Nasser
2001-07-25 15:35 ` Michael Snyder
2001-07-25 15:41 ` Fernando Nasser
2001-07-25 15:46 ` Michael Snyder
-- strict thread matches above, loose matches on Subject: below --
2001-07-07 11:57 Michael Elizabeth Chastain
2001-07-02 18:13 Michael Elizabeth Chastain
2001-07-05 8:09 ` Andrew Cagney
2001-07-05 11:32 ` Michael Snyder
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=3B44982C.4090005@cygnus.com \
--to=ac131313@cygnus.com \
--cc=chastain@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=msnyder@cygnus.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