From: Daniel Jacobowitz <drow@false.org>
To: Michael Elizabeth Chastain <mec.gnu@mindspring.com>
Cc: cagney@gnu.org, gdb-patches@sources.redhat.com, jimb@redhat.com,
keiths@redhat.com
Subject: Re: RFA: patch to fix gdb/1680
Date: Fri, 18 Jun 2004 20:33:00 -0000 [thread overview]
Message-ID: <20040618203304.GA30844@nevyn.them.org> (raw)
In-Reply-To: <20040618202524.608064B104@berman.michael-chastain.com>
On Fri, Jun 18, 2004 at 04:25:24PM -0400, Michael Chastain wrote:
> drow> I prefer to solve the mystery instead.
>
> We can do both. I don't want to have 16 ERROR's in my face while
> we are figuring this out.
>
> drow> Presumably this version of TCL does not put special meaning on
> drow> {string}, but does on {NUMBER}, as has become fashionable for regex
> drow> engines.
>
> Aw, foo! That's what's different about gdb.cp/*.exp. All the examples
> in gdb.cp/*.exp are like:
>
> { x = 100, y = 101 }
>
> Both the sourceware version of TCL (which is based on 8.4.1) and
> the version I use of TCL (8.4.6) have code for {NUMBER} and
> {NUMBER, NUMBER} modifiers.
>
> I suspect there's some difference happening at the expect level
> (5.26 versus 5.41).
>
> Time to dive into the TCL source and throw in some fprintf's and stuff.
The correct change is to use { \{ } } or " \\{ } "; it is harmless but
still incorrect where we use "\{ }" or "{ }" in the C++ testsuite.
I imagine it depends on the guts of the regex matcher whether " { 2, 0,
4 }" throws an error.
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-06-18 20:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-18 20:25 Michael Elizabeth Chastain
2004-06-18 20:33 ` Daniel Jacobowitz [this message]
-- 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 19:43 Michael Elizabeth Chastain
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
2004-06-18 22:20 ` Jim Blandy
2004-06-18 22:51 ` Andreas Schwab
2004-06-19 6:15 ` Jim Blandy
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=20040618203304.GA30844@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