From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3887 invoked by alias); 30 Aug 2002 19:31:32 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 3879 invoked from network); 30 Aug 2002 19:31:31 -0000 Received: from unknown (HELO localhost.redhat.com) (66.30.197.194) by sources.redhat.com with SMTP; 30 Aug 2002 19:31:31 -0000 Received: from ges.redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 5F1EF3C67; Fri, 30 Aug 2002 15:31:31 -0400 (EDT) Message-ID: <3D6FC813.6050203@ges.redhat.com> Date: Fri, 30 Aug 2002 12:39:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.0) Gecko/20020824 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Michael Snyder Cc: Jim Blandy , Daniel Jacobowitz , gdb-patches@sources.redhat.com Subject: Re: [Jim Blandy ] Re: RFA: test GDB's ability to kill threaded programs that die messily References: <3D6EBCB4.B97D8DA3@redhat.com> <20020830004234.GA1540@nevyn.them.org> <3D6FB5A2.351A1D90@redhat.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-08/txt/msg01043.txt.bz2 > Jim Blandy wrote: > >> >> Daniel Jacobowitz 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