From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 103943 invoked by alias); 1 Jun 2018 17:27:44 -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 103907 invoked by uid 89); 1 Jun 2018 17:27:42 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy= 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; Fri, 01 Jun 2018 17:27:41 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id EEFBD560E7 for ; Fri, 1 Jun 2018 13:27:39 -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 8wrHYeEoOsZH for ; Fri, 1 Jun 2018 13:27:39 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id BB78E560E6 for ; Fri, 1 Jun 2018 13:27:39 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id 07468808EA; Fri, 1 Jun 2018 10:27:38 -0700 (PDT) Date: Fri, 01 Jun 2018 17:27:00 -0000 From: Joel Brobecker To: gdb-patches@sourceware.org Subject: Re: NEED FEEDBACK: time to start the GDB 8.2 release process (2018-05-30 update) Message-ID: <20180601172737.fvdog4t3ofxqdv7l@adacore.com> References: <20180530225306.jbf5xtpgvkmno7md@adacore.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180530225306.jbf5xtpgvkmno7md@adacore.com> User-Agent: NeoMutt/20170113 (1.7.2) X-SW-Source: 2018-06/txt/msg00027.txt.bz2 > Does anyone have projects that are nearly finished and would be > important to include in 8.2 rather than wait for 8.3? If yes, > what kind of time frame can we expect for getting those in. > Should we wait for the patch to be in master before we cut the branch, > or can the changes be backported afterwards? I am thinking we should also include the following patch: gdb: Don't drop SIGSTOP during stop_all_threads https://www.sourceware.org/ml/gdb-patches/2018-05/msg00401.html This one causes GDB to (sometimes) hang while trying to attach to a process. Unfortunately, the while the patch looks fairly simple, I think it needs careful review from someone who knows this area well... -- Joel