From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca (simark.ca [158.69.221.121]) by sourceware.org (Postfix) with ESMTPS id ECD0138485B7 for ; Tue, 24 May 2022 15:18:05 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org ECD0138485B7 Received: from [172.16.0.144] (192-222-180-24.qc.cable.ebox.net [192.222.180.24]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPSA id 8071E1E143; Tue, 24 May 2022 11:18:05 -0400 (EDT) Message-ID: <5ffd5107-ed8f-f356-52a1-8e43d2fc1c1e@simark.ca> Date: Tue, 24 May 2022 11:18:04 -0400 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.9.0 Subject: Re: [PATCH 0/2] gdb: Fix DUPLICATE and PATH regressions throughout Content-Language: fr To: Pedro Alves , gdb-patches@sourceware.org References: <20220519123445.2756177-1-pedro@palves.net> From: Simon Marchi In-Reply-To: <20220519123445.2756177-1-pedro@palves.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-7.3 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, NICE_REPLY_A, SPF_HELO_PASS, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) 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, 24 May 2022 15:18:07 -0000 On 5/19/22 08:34, Pedro Alves wrote: > Patch #1 adds "gdb_test -nopass" as mentioned here: > > https://sourceware.org/pipermail/gdb-patches/2022-May/189189.html > > Patch #2 fixes DUPLICATE/PATH regressions throughout. I only read the commit messages, and that all makes sense to me. I am seeing a lot of failures on my CI due to this (it counts new DUPLICATEs as failures), so this will help a lot bring it back to green. Simon