Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Andrew Cagney <cagney@gnu.org>
Cc: Michael Elizabeth Chastain <mec.gnu@mindspring.com>,
	jimb@redhat.com, gdb-patches@sources.redhat.com,
	Keith Seitz <keiths@redhat.com>
Subject: Re: RFA: patch to fix gdb/1680
Date: Fri, 18 Jun 2004 20:00:00 -0000	[thread overview]
Message-ID: <20040618200036.GA29729@nevyn.them.org> (raw)
In-Reply-To: <40D348FA.2070009@gnu.org>

On Fri, Jun 18, 2004 at 03:56:42PM -0400, Andrew Cagney wrote:
> >>Try "{}" instead of {""}.  In these sorts of situtations that works a
> >>>lot better.
> >
> >
> >which is the missing bit of my suggestion.  { and \{ are the same thing
> >when written in double quotes.  So (since we can't use {} here, because
> >there is a variable substitution inside gdb_test's argument), use two
> >backslashes.  That way one will reach the regex engine.
> 
> (two many quote characters).  Use ``{ ... }'' instead of ``" ... "'' 
> when wrapping things up, it avoids the entire quoting et.al. problem.

I wrote:
> >when written in double quotes.  So (since we can't use {} here, because
> >there is a variable substitution inside gdb_test's argument), use two

If we use { }, the $r will not be expanded, and the test will not work. 
We can't use { } for this.

-- 
Daniel Jacobowitz


  reply	other threads:[~2004-06-18 20:00 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-18 19:18 Michael Elizabeth Chastain
2004-06-18 19:35 ` Andrew Cagney
2004-06-18 19:42 ` Daniel Jacobowitz
2004-06-18 19:56   ` Andrew Cagney
2004-06-18 20:00     ` Daniel Jacobowitz [this message]
2004-06-18 22:20   ` Jim Blandy
2004-06-18 22:51     ` Andreas Schwab
2004-06-19  6:15       ` Jim Blandy
  -- strict thread matches above, loose matches on Subject: below --
2004-06-21  2:44 Michael Elizabeth Chastain
     [not found] <1087626323.4926.ezmlm@sources.redhat.com>
2004-06-20 22:37 ` Jim Ingham
2004-06-19  6:31 Michael Elizabeth Chastain
2004-06-21  5:00 ` Jim Blandy
2004-06-19  2:44 Michael Elizabeth Chastain
2004-06-19  6:25 ` Joel Brobecker
2004-06-18 23:38 Michael Elizabeth Chastain
2004-06-18 20:25 Michael Elizabeth Chastain
2004-06-18 20:33 ` Daniel Jacobowitz
2004-06-18 19:43 Michael Elizabeth Chastain
2004-06-18 18:25 Michael Elizabeth Chastain
2004-06-18 18:10 Jim Blandy
2004-06-18 18:42 ` 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=20040618200036.GA29729@nevyn.them.org \
    --to=drow@false.org \
    --cc=cagney@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@redhat.com \
    --cc=keiths@redhat.com \
    --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