From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: ac131313@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] Rewrite "structs" testcase
Date: Wed, 12 Nov 2003 16:51:00 -0000 [thread overview]
Message-ID: <20031112165100.ED9F14B361@berman.michael-chastain.com> (raw)
I'm getting 508 PASS / 71 KFAIL with three configurations,
but I'm getting 504 PASS / 4 FAIL / 71 KFAIL with gcc 3.3.2 -gdwarf-2.
The FAILs are
# gcc 3.3.2, binutils 2.14, -gdwarf-2
p/c fun2()
$1 = {a = 97 'a', b = 0 '\0'}
(gdb) FAIL: gdb.base/structs.exp: p/c fun2(); call 2 structs-tc-tll
p/c L2
$2 = {a = 97 'a', b = 0 '\0'}
(gdb) FAIL: gdb.base/structs.exp: p/c L2; call 2 structs-tc-tll
p/c fun2()
$1 = {a = 97 'a', b = 0 '\0'}
(gdb) FAIL: gdb.base/structs.exp: p/c fun2(); call 2 structs-tc-td
p/c L2
$2 = {a = 97 'a', b = 0 '\0'}
(gdb) FAIL: gdb.base/structs.exp: p/c L2; call 2 structs-tc-td
Do these look like bugs in the script or bugs in gdb? If they are
bugs in gdb then the test script is doing a good job.
Michael C
next reply other threads:[~2003-11-12 16:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-12 16:51 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-11-12 18:30 Michael Elizabeth Chastain
2003-11-12 18:13 Michael Elizabeth Chastain
2003-11-13 16:11 ` Andrew Cagney
2003-11-17 15:59 ` Andrew Cagney
2003-11-20 17:17 ` Andrew Cagney
2003-11-08 1:05 Michael Elizabeth Chastain
2003-11-09 1:22 ` Andrew Cagney
2003-11-10 0:32 ` Michael Elizabeth Chastain
2003-11-11 22:28 ` Andrew Cagney
2003-11-06 20:44 Michael Elizabeth Chastain
2003-11-07 20:35 ` Andrew Cagney
2003-11-06 19:10 Michael Elizabeth Chastain
2003-11-06 20:22 ` Andrew Cagney
2003-11-06 17:33 Michael Elizabeth Chastain
2003-11-06 18:49 ` Andrew Cagney
2003-11-06 21:38 ` Michael Snyder
2003-11-05 22:17 Andrew Cagney
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=20031112165100.ED9F14B361@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=ac131313@redhat.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