From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6398 invoked by alias); 11 Apr 2017 01:18:07 -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 6381 invoked by uid 89); 11 Apr 2017 01:18:06 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=me!, thatll, that'll, tentative 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 ESMTP; Tue, 11 Apr 2017 01:18:05 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 3C8E85A388; Mon, 10 Apr 2017 21:18:05 -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 zrtiWat6ppex; Mon, 10 Apr 2017 21:18:05 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 0E2905A361; Mon, 10 Apr 2017 21:18:04 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id DBCAF640F6; Mon, 10 Apr 2017 18:18:02 -0700 (PDT) Date: Tue, 11 Apr 2017 01:18:00 -0000 From: Joel Brobecker To: gdb-patches@sourceware.org, Sergio Durigan Junior Cc: antoine.tremblay@ericsson.com, mishra.nitish.88@gmail.com Subject: GDB 8.0 release / imminent branching? (2017-04-10) Message-ID: <20170411011802.s24zz4pygnt2qoyg@adacore.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.6.2-neo (2016-08-21) X-SW-Source: 2017-04/txt/msg00256.txt.bz2 Hello, We're now about 4 weeks after our tentative branching date, and I am concerned that if we continue to wait for some of the pending issues to be resolved, we'll have new issues appearing on master that'll might delay the branching further. So I'd like to propose we branch in the next couple of days, and then backport fixes, so as to stabilize the branch. We have two 8.0 pending PRs: * server/21169 GDBServer on ARM can crash the inferior while single stepping Antoine indicated that he's working on it, and his expected completion date isn't all that far away. Still on track for that, Antoine? * build/21187 Static linking of libstdc++ and libgcc with GDB leads to broken exception handling on AIX platform For this one, I think the feedback so far is a question about the fact that this is only a work around. Parallel to that, did I see a thread where people are discussing a real fix for the exception handling issue? So, perhaps we might not need the GDB patch after all? Is there a version of GCC capable of compiling GDB 8.x on AiX? Then, there is the issue of the Python APIs for record and btrace. It sounds like we're getting close? Perhaps what we could do is also backport the changes once the an agreement has been reached? And finally, there is the build-bot. I'm having trouble using the interface and understanding whether the current overall state is rather positive or negative. Sergio, would you be able to help me? If all good, I could create the branch with a SHA1 that you'd give me! Thank you! -- Joel