Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@cygnus.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Michael Elizabeth Chastain <chastain@cygnus.com>,
	gdb-patches@sources.redhat.com
Subject: Re: [PATCH] quoting curly braces in call-rt-st
Date: Thu, 05 Jul 2001 11:32:00 -0000	[thread overview]
Message-ID: <3B44B2AD.1E28EEA9@cygnus.com> (raw)
In-Reply-To: <3B44830E.7080106@cygnus.com>

Andrew Cagney wrote:
> 
> Um,
> 
> Why are these patterns mysteriously breaking now.  call-ar-st has been
> in the repository for a very long time.

I don't think this is anything new.  Call-ar-st has always been
a source of mysterious and erratic fails (at least for me).

> 
> For what its worth I was having fun running expect on Red Hat 7.x.
> Zapping the expect built from CVS so that the pre-installed expect was
> used mysteriously eliminated the problem.

I know it's an expect issue -- I'm just trying to work around it.

> If this is trying to address that same problem then I don't think it is
> a bug in GDB's patterns.  Rather it is a bug in how expect was being built.

Yep, it's a work-around for an expect issue.  But we do that
all the time.


  reply	other threads:[~2001-07-05 11:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-02 18:13 Michael Elizabeth Chastain
2001-07-05  8:09 ` Andrew Cagney
2001-07-05 11:32   ` Michael Snyder [this message]
2001-07-05  8:34 Michael Elizabeth Chastain
2001-07-05 10:11 ` Andrew Cagney
2001-07-07 11:57 Michael Elizabeth Chastain
     [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

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=3B44B2AD.1E28EEA9@cygnus.com \
    --to=msnyder@cygnus.com \
    --cc=ac131313@cygnus.com \
    --cc=chastain@cygnus.com \
    --cc=gdb-patches@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