From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: drow@false.org, jimb@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: patch to fix gdb/1680
Date: Fri, 18 Jun 2004 19:18:00 -0000 [thread overview]
Message-ID: <20040618191836.629204B104@berman.michael-chastain.com> (raw)
drow> Does it work if you put a backslash in front of them instead? That's
drow> clearer to read, IMO.
On my machine (expect 5.41):
"{...}" ERROR: Process no longer exists
"\{...\}" ERROR: Process no longer exists
"\\{...\\}" Works fine
> This had better work, or the entire C++ testsuite is in trouble.
Something freaky is going on, indeed.
Empirically, the C++ test suite is working fine. For example,
these tests:
# gdb.cp/class2.exp
# Access the "A" object.
gdb_test "print alpha" \
"= {.*a1 = 100.*}" \
"print alpha at marker return 0"
# Access the "B" object.
gdb_test "print beta" \
"= {.*a1 = 200.*b1 = 201.*b2 = 202}" \
"print beta at marker return 0"
# gdb.cp/derivation.exp
gdb_test "print a_instance" "\\$\[0-9\]+ = \{a = 1, aa = 2\}" "print value of a_instance"
# gdb.cp/userdef.exp
gdb_test "print one - two" "\\\$\[0-9\]* = {x = -2, y = -2}"
gdb_test "print one * two" "\\\$\[0-9\]* = {x = 8, y = 15}"
gdb_test "print one / two" "\\\$\[0-9\]* = {x = 0, y = 0}"
gdb_test "print one % two" "\\\$\[0-9\]* = {x = 2, y = 3}"
I spent about two hours playing with the braces in i386-sse.exp.
I truly don't understand why the code i386-sse.exp barfs out when
all that code in gdb.cp/*.exp works. But I'm sure it works on
my systems (native i686-pc-linux-gnu and native hppa2.0w-hp-hpux11.11),
with expect 5.41. And it's working on other people's systems in
gdb-testers@ ; I presume most of those results are with the sourceware
version of expect (based on expect 5.26).
I definitely want Jim's patch so that i386-sse.exp does its job.
If you insist, we could make PR gdb/1680 suspended instead of
closing it, to remind us of this unsolved mystery.
Michael C
next reply other threads:[~2004-06-18 19:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-18 19:18 Michael Elizabeth Chastain [this message]
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
-- 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=20040618191836.629204B104@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@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