From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 50237 invoked by alias); 1 Feb 2016 03:06:47 -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 50221 invoked by uid 89); 1 Feb 2016 03:06:46 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.8 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE autolearn=no version=3.3.2 spammy=champion, hesitant, sometime, 711 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; Mon, 01 Feb 2016 03:06:45 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 412801166BA; Sun, 31 Jan 2016 22:06:43 -0500 (EST) 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 Wi9vYmxc4JHM; Sun, 31 Jan 2016 22:06:43 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id C7821116640; Sun, 31 Jan 2016 22:06:42 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id 7785D407D2; Mon, 1 Feb 2016 07:06:38 +0400 (RET) Date: Mon, 01 Feb 2016 03:06:00 -0000 From: Joel Brobecker To: gdb-patches@sourceware.org, sergiodj@redhat.com, Yao Qi , Pedro Alves , keiths@redhat.com Subject: RFC: branching for GDB 7.11 soon? (possibly Wed) Message-ID: <20160201030638.GG4008@adacore.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.23 (2014-03-12) X-SW-Source: 2016-02/txt/msg00000.txt.bz2 Hello everyone, According to the GDB 7.11 release cycle wiki page (https://sourceware.org/gdb/wiki/GDB_7.11_Release), there no longer any items that are explicitly marked as being blocking for branching. We do have a few "maybe"-s. There are also 3 PRs filed with a target-milestone of GDB 7.11. From experience, if we want them to make a given release, they need to have a champion. Currently unassigned, we have: PR19474 "break LINE_NUM" set breakpoint on file other than current source file (suggest Keith?) PR19503 internal-error: linux_nat_resume: Assertion `lp != NULL' failed. (Pedro seems to be on it already) In addition, we have the following PR, which Keith already sent a patch: PR19506 Regression with gdb.Breakpoint("*") At the moment, I would be hesitant to branch before we first analyze what would be required to fix PR19474 ("break LINE_NUM"). But if we're confident that it can be fairly safely fixed on the branch, I don't see any other issue blocking for branching, which I would then propose to be doing sometime early Wed. Sergio - would you be able to give us a rough description of how good the results are in the buildbots? Anything we should be aware of for this release? (Thanks!) Thoughts? -- Joel