From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 47796 invoked by alias); 7 Jul 2015 13:25:09 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 47786 invoked by uid 89); 7 Jul 2015 13:25:08 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.2 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY autolearn=no version=3.3.2 X-HELO: rock.gnat.com Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Tue, 07 Jul 2015 13:25:02 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 95B482863B; Tue, 7 Jul 2015 09:25:00 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id KfxcLoDjiIqv; Tue, 7 Jul 2015 09:25:00 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 5CE58285F7; Tue, 7 Jul 2015 09:25:00 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id 08FC041C8C; Tue, 7 Jul 2015 06:24:59 -0700 (PDT) Date: Tue, 07 Jul 2015 13:25:00 -0000 From: Joel Brobecker To: Simon Marchi , Pedro Alves Cc: gdb-patches Subject: Re: Should this be on the blocker list for the 7.10 release? Message-ID: <20150707132459.GA16734@adacore.com> References: <559AE482.1010109@ericsson.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <559AE482.1010109@ericsson.com> User-Agent: Mutt/1.5.23 (2014-03-12) X-SW-Source: 2015-07/txt/msg00171.txt.bz2 > I filed this bug recently: > > https://sourceware.org/bugzilla/show_bug.cgi?id=18600 > > In short, gdb sometimes leaves stopped newly spawned threads created by a > fork child. The "sometimes" happens quite often, so it's very easy to > reproduce. This has the effect of leaving (part) of your program stopped > while you expect it to be running. "info threads" shows the threads as > running while in reality they aren't. > > Is this bug serious enough to be on the blocking list for 7.10? I would > think so, as it's a regression compared to 7.9. However, I don't want > to impose work on anybody (e.g. Pedro, or anybody else familiar with the > linux-nat subsystem), which is why I am asking. I am willing to put time > on this, but the chances of me successfully fixing the bug are quite slim. Not sure. I think Pedro would be in a better position to answer. For now, I've put this issue as a "maybe" for 7.10; so we will not release until this is fixed, or we explicitly decide it's OK for 7.10. Pedro? -- Joel