From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ua1-x929.google.com (mail-ua1-x929.google.com [IPv6:2607:f8b0:4864:20::929]) by sourceware.org (Postfix) with ESMTPS id 8FAC6385742B for ; Mon, 31 May 2021 17:43:15 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 8FAC6385742B Received: by mail-ua1-x929.google.com with SMTP id 68so6974441uao.11 for ; Mon, 31 May 2021 10:43:15 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=rmJrX6FCZ7+cfgEo47IJjSvnhz10Kqkl9nbAjH6jTIw=; b=eFE/nfmlv/MlOY1X6SlPTFZ8t04phB+ay35XW83zNAjKMQePdRoDBTY+4lm8Mo+H5s FwaPvnvKVnt/GN+EP9V4o872z+oif0HAfpG9LN8WAqpzKViFi6X3s5NvHGlVEjTBzUd3 O8fTaTe0E1dBs7r3Of6pmSUKCAzKzt/eONflgczExeM3L8RBsoAddyOhwpnjtY8AUOLz o4KT04QIxJq8nGmgxBS0ka49xiyxerDlPTiFyM2yHqFCVsEYq3OKRGim41+BZrkBJnho wXbQkMs4sWOmhR1FsIGNRRCveu90yGtenYZmFrPLL74vXgGsRkQ7NParKHUw+9h2Mfeh gyvA== X-Gm-Message-State: AOAM532suEik12IoMXCrePGwvYSgwUX4NdL1c+MCDnmCo/LW5ofNTXVK OfqMJHOz7FUYiad/ih49+wjCFQDywW54puQqfUo067XyVb9r/Q== X-Google-Smtp-Source: ABdhPJzJf6YR1WGg5V8cR5WAnHnSKdDeHOMawFiptbnEo6EdOksNAYvc1GhxQHIJI6zk/IhWOx4Ms55ilupMVOwAIbw= X-Received: by 2002:ab0:284a:: with SMTP id c10mr11797062uaq.106.1622482995168; Mon, 31 May 2021 10:43:15 -0700 (PDT) MIME-Version: 1.0 References: <20210517162137.GA88579@adacore.com> <20210521185856.GS31252@adacore.com> In-Reply-To: <20210521185856.GS31252@adacore.com> From: Emil Velikov Date: Mon, 31 May 2021 18:43:03 +0100 Message-ID: Subject: Re: Backport 037e8112b97 for the 10.x branch To: Joel Brobecker Cc: Emil Velikov via Gdb Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-1.6 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: gdb@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 May 2021 17:43:17 -0000 On Fri, 21 May 2021 at 21:01, Joel Brobecker wrote: > > > > We are not planning on doing another 10.x release, so would that > > > still be useful for you to do? > > > > > Yes, it would. > > > > > Note that we're started the process of preparing for the GDB 11.1 > > > release. It's really hard to predict how long it's going to take > > > before we release, considering that we are a volunteer project, > > > but I'm hoping a couple of months. > > > > > Realising that I'm pushing my luck, I would warmly encourage you to do > > another 10.x release. > > Partially due to the severity of the bug - anything built with -m32 is > > affected - and partially due to how wide-spread the 10.x series is. > > > > >From a casual look at repology [1] the following distributions are > > affected and a bunch of them will be "stuck" with the 10.x series. > > Thus I do think it will be of great benefit in having another 10.x > > with said fix - even if only this patch is included. > > > > List of distributions using GDB 10.x alongside 5.9+ kernel - Alpine, > > Arch, Debian testing, Fedora 33&34, openSUSE Leap 15.x, Ubuntu 21.04 > > ... and their respective derivatives. > > > > Thanks for your time and dedication improving GDB. > > Typically, Linux distributions build a modified version of GDB, > with a number of addition patches. So, while I'm open to the idea > of creating another corrective release in general, I'm not certain > we have a sufficiently strong reason in this case. If there is > a stronger push, perhaps... > > In the meantime, if you'd like, you can certainly ask on the gdb-patches > mailing-list for permission to backport this patch to the gdb-10-branch. > If given, before you can backport it, you'll need to create a GDB PR > in bugzilla (https://sourceware.org/bugzilla/) so as to document this > issue, and then ammend the commit message to include that PR number, > e.g. like this commit: > > | gdb/ChangeLog: > | > | PR gdb/27614 > | * contrib/gdb-add-index.sh: Fix when called with a symlink as an > | argument. > > We'll also need to ask someone to create a 10.3 milestone and > set the Target Milestone field to that new milestone. > > The PR is there to help us track precisely what changes went in > the various corrective releases, and doing the above is part of > our procedures for backporting changes to those corrective releases. > Is this above process documented and accessbile from the GDB website somewhere? IMHO it is something which should be dead easy to find - see for example what we've done for mesa. Thanks for the instructions Joel, will get back to this later in the week. -Emil [1] https://www.google.com/search?q=mesa+stable+patch+backport