From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: cagney@gnu.org, keiths@redhat.com, mec.gnu@mindspring.com
Cc: drow@false.org, gdb-patches@sources.redhat.com, jimb@redhat.com
Subject: Re: RFA: patch to fix gdb/1680
Date: Fri, 18 Jun 2004 19:43:00 -0000 [thread overview]
Message-ID: <20040618194350.BD21A4B104@berman.michael-chastain.com> (raw)
Literally, the test that blows up is:
foreach r {0 1 2 3 4 5 6 7} {
gdb_test "print \$xmm$r.v4_float" \
".. = {$r, $r.25, $r.5, $r.75}.*" \
"check contents of %xmm$r"
}
I ripped out most of the other meta-characters and this still blows up:
gdb_test "print xmm0.v4_float" \
".. = {0, 0.25, 0.5, 0.75}.*" \
"check contents of xmm0"
"blows up" means:
ERROR: Process no longer exists
What Daniel is saying, and I'm agreeing, is that gdb.cp/*.exp
has a lot of similar tests. And they are not blowing up.
Michael C
next reply other threads:[~2004-06-18 19:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-18 19:43 Michael Elizabeth Chastain [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 20:25 Michael Elizabeth Chastain
2004-06-18 20:33 ` Daniel Jacobowitz
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=20040618194350.BD21A4B104@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=cagney@gnu.org \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@redhat.com \
--cc=keiths@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