From: Michael Elizabeth Chastain <mec@shout.net>
To: ac131313@redhat.com
Cc: carlton@kealia.com, gdb-patches@sources.redhat.com
Subject: Re: [testsuite] add gdb.cp/gdb1355.exp
Date: Sat, 20 Sep 2003 22:03:00 -0000 [thread overview]
Message-ID: <200309202203.h8KM3GMb006836@duracef.shout.net> (raw)
mec> Neither. Just agreeing with what I'm assuming is David's assertion that
mec> KFAIL and XFAIL both lead to people sweeping problems under the carpet.
Okay, I see.
I'm gonna go with FAIL because David likes it better and I'm
pretty neutral.
ac> Judgment call. If its possible for gdb to identify the corrupt input
ac> then it needs to alert the user to the problem, and failing to do this
ac> is a bug.
I agree, but I don't have the resources to pursue this line of
inquiry.
Michael C
next reply other threads:[~2003-09-20 22:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-20 22:03 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-20 21:59 Michael Elizabeth Chastain
2003-09-18 21:27 Michael Elizabeth Chastain
2003-09-20 21:46 ` Andrew Cagney
2003-09-20 22:31 ` Daniel Jacobowitz
2003-09-21 0:51 ` Andrew Cagney
2003-09-18 21:22 Michael Elizabeth Chastain
2003-09-18 15:33 Michael Elizabeth Chastain
2003-09-20 21:40 ` Andrew Cagney
2003-09-18 2:01 Michael Elizabeth Chastain
2003-09-18 14:27 ` Andrew Cagney
2003-09-18 16:05 ` David Carlton
2003-09-18 15:38 ` David Carlton
2003-09-18 0:54 Michael Elizabeth Chastain
2003-09-18 0:56 ` Daniel Jacobowitz
2003-09-18 1:20 ` David Carlton
2003-09-18 1:27 ` David Carlton
2003-09-18 0:00 Michael Elizabeth Chastain
2003-09-18 0:48 ` David Carlton
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=200309202203.h8KM3GMb006836@duracef.shout.net \
--to=mec@shout.net \
--cc=ac131313@redhat.com \
--cc=carlton@kealia.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