From: Jim Blandy <jimb@redhat.com>
To: Andrew Cagney <ac131313@ges.redhat.com>
Cc: Michael Snyder <msnyder@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: Thu, 05 Sep 2002 12:45:00 -0000 [thread overview]
Message-ID: <vt2ofbcqlmp.fsf@zenia.red-bean.com> (raw)
In-Reply-To: <3D73C106.9060302@ges.redhat.com>
Andrew Cagney <ac131313@ges.redhat.com> writes:
> >> > 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?
> >
> >> I've marked up the tests with commented-out setup_kfail forms that
> >> refer to the bug number, and included the bug number in the test
> >> name. I thought that's how we'd decided to handle these.
> > OK, your recollection is echoed by Andrew.
> > I'm happy now. Please check it in.
>
> Hmm, thinking about it, the message proper, until setup_kfail is
> added, should include text like ``(known bug gdb/NNNN)'' so people
> don't go chasing after known problems.
It's not the chasing down we want to avoid --- we want to encourage
that. :) Rather, it's that we want to make clear that this bug is not
a regression.
I've changed the message from:
GDB exits after multi-threaded program exits messily (gdb/568)
to:
GDB exits after multi-threaded program exits messily (not a regression; gdb/568)
prev parent reply other threads:[~2002-09-05 19:45 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
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 [this message]
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=vt2ofbcqlmp.fsf@zenia.red-bean.com \
--to=jimb@redhat.com \
--cc=ac131313@ges.redhat.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.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