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 1AC1C3844079 for ; Fri, 3 Jul 2020 15:12:07 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 1AC1C3844079 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=simark.ca Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=simark@simark.ca Received: from [172.16.0.95] (192-222-181-218.qc.cable.ebox.net [192.222.181.218]) (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 7EC5A1E111; Fri, 3 Jul 2020 11:12:06 -0400 (EDT) Subject: Re: GDB 10 branching - 2020-06-27 Update To: Joel Brobecker Cc: gdb-patches@sourceware.org, Tom Tromey References: <20200627154005.GA5618@adacore.com> <1e871f06-d788-49c1-6185-18ac2b977908@simark.ca> <20200703151016.GL5340@adacore.com> From: Simon Marchi Message-ID: Date: Fri, 3 Jul 2020 11:12:05 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.8.0 MIME-Version: 1.0 In-Reply-To: <20200703151016.GL5340@adacore.com> Content-Type: text/plain; charset=utf-8 Content-Language: tl Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-7.7 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, SPF_HELO_PASS, 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-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: Fri, 03 Jul 2020 15:12:08 -0000 On 2020-07-03 11:10 a.m., Joel Brobecker wrote: >> I stumbled on a bug introduced by the multi-target patch, which I >> think should be a blocker for the release (not necessarily the >> branching). I marked it with target milestone 10.1 in bugzilla: >> >> https://sourceware.org/bugzilla/show_bug.cgi?id=26199 > > Thanks Simon. Will you be the one actually looking into the problem? > I would understand if not (for whatever reason); knowing it would then > allow us to start searching for someone who could look into it. I notified Pedro about it, he and/or I will look into it. Simon