From: Andrew Cagney <ac131313@ges.redhat.com>
To: Michael Snyder <msnyder@redhat.com>
Cc: Jim Blandy <jimb@redhat.com>, Daniel Jacobowitz <drow@mvista.com>,
gdb-patches@sources.redhat.com
Subject: Re: [Jim Blandy <jimb@redhat.com>] Re: RFA: test GDB's ability to kill threaded programs that die messily
Date: Fri, 30 Aug 2002 12:39:00 -0000 [thread overview]
Message-ID: <3D6FC813.6050203@ges.redhat.com> (raw)
In-Reply-To: <3D6FB5A2.351A1D90@redhat.com>
> Jim Blandy wrote:
>
>>
>> Daniel Jacobowitz <drow@mvista.com> writes:
>
>> > On Thu, Aug 29, 2002 at 05:30:44PM -0700, Michael Snyder wrote:
>
>> > > Jim Blandy wrote:
>
>> > > >
>> > > > Okay --- I've committed the portable thread compilation support that
>> > > > this patch depends on. May I commit this test?
>
>> > >
>> > > The test is fine. But I missed the fix. Has a fix been committed?
>> > > If you wouldn't mind, could you give me a pointer?
>
>> >
>> > I don't think there is a fix; this test is related to the same PR as my
>> > ugly warning workaround.
>
>>
>> Yes, there is no fix.
>
>
> Didn't we decide that if there's an unfixed bug, you file a bug report,
> but you don't check in a test that will fail?
This is why we're introducing KFAIL (I think some doco needs to be
updated). In the mean time, I'm not sure what the maintainer policy is.
I believe its to include a line like:
# setup_kfail gdb/NNNN
just before the test.
Andrew
next prev parent reply other threads:[~2002-08-30 19:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-29 15:48 Jim Blandy
2002-08-29 17:41 ` Michael Snyder
2002-08-29 18:58 ` Daniel Jacobowitz
2002-08-30 7:32 ` Jim Blandy
2002-08-30 11:29 ` Michael Snyder
2002-08-30 12:39 ` Andrew Cagney [this message]
2002-08-30 14:39 ` Jim Blandy
2002-08-30 15:22 ` Michael Snyder
2002-09-02 12:51 ` Andrew Cagney
2002-09-05 12:45 ` Jim Blandy
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=3D6FC813.6050203@ges.redhat.com \
--to=ac131313@ges.redhat.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@redhat.com \
--cc=msnyder@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