From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr1-x436.google.com (mail-wr1-x436.google.com [IPv6:2a00:1450:4864:20::436]) by sourceware.org (Postfix) with ESMTPS id 115CC3858409 for ; Tue, 23 Nov 2021 04:54:13 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 115CC3858409 Received: by mail-wr1-x436.google.com with SMTP id b12so36658372wrh.4 for ; Mon, 22 Nov 2021 20:54:13 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=FS9eG23X2OB/OrnqFyI5CSkcaJ/bSvvyVTjl9+fDJ8E=; b=WyDm+kfIZ0pIGAzHBiYB7C+lpwyP7tZe4PaUtmzQwFVTafiuM6X2Bl2x60Mafj5d2s PBaaz7XLN5Kr7i4Qlvc0ioOUS1WoeADynH6YaLL7ozC1uvm9Kk4yUJU//NWKXnAXS7E0 kN2vYppyuyrBk9wCNA7p4ge/IWcmjI5fYppq98Ljwfb5QpZpixLPPBiSHc5LPNDHqMVP 3BnzikVcDeeRRGKK3aokmnVNa/PpJWeRiJ7Dg6Kpfd1M0QSBXJM9yjBpP4iJO7XwGxSG ybJ3WNF6es2511efIuerbLp1kV2xmZB2YG91d5ZJCv7ZqmCu1BjiKa674Q4h3um/hw6/ 2yRQ== X-Gm-Message-State: AOAM533QGHsrU5ULtHP59O+li40SjrSspM3TVfd/DZE8Xv9ZMCUlQHs6 pjxgDVtX74Y6auWMDn2nxtX7 X-Google-Smtp-Source: ABdhPJxLmC90aueXT4CWS1VxXF9gOYWOhcM9O+nwDc4Y2u4nNBK6NjLSlY5qCh4/ZB35w0jqx7sD7Q== X-Received: by 2002:a5d:5984:: with SMTP id n4mr3641432wri.23.1637643251819; Mon, 22 Nov 2021 20:54:11 -0800 (PST) Received: from takamaka.home (lfbn-reu-1-483-157.w92-130.abo.wanadoo.fr. [92.130.72.157]) by smtp.gmail.com with ESMTPSA id h17sm10901635wrp.34.2021.11.22.20.54.11 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 22 Nov 2021 20:54:11 -0800 (PST) Received: by takamaka.home (Postfix, from userid 1000) id 0F13DA49DA; Tue, 23 Nov 2021 08:54:09 +0400 (+04) Date: Tue, 23 Nov 2021 08:54:09 +0400 From: Joel Brobecker To: Bruno Larsen Cc: Joel Brobecker , gdb-patches@sourceware.org Subject: Re: GDB 11.2 ("re-spin") update (2021-11-21) Message-ID: References: <252590db-4a8f-68ac-fad5-382783e5ea02@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <252590db-4a8f-68ac-fad5-382783e5ea02@redhat.com> X-Spam-Status: No, score=-4.0 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2021 04:54:14 -0000 Hi Bruno, > I'm wondering if PR 28480 > (https://sourceware.org/bugzilla/show_bug.cgi?id=28480) is relevant > enough to be on .2; A solution is already on the list > (https://sourceware.org/pipermail/gdb-patches/2021-November/183243.html) > but hasn't been accepted yet > > Basically, with this proposed solutions, things will stop breaking > silently and will now loudly warn if ambiguous requests are made. This seems reasonable to me, provided the patch doesn't drag for too long, and then a Global Maintainer approves the patch for backporting to 11.2 (it looks relatively contained, so no objection a priori myself, but I don't know much about this area of the code). The PR suggests this is a regression from GDB 10, but it sounds like it was really luck of the draw that made it work before? -- Joel