From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <eliz@gnu.org>
Received: from eggs.gnu.org (eggs.gnu.org [209.51.188.92])
 by sourceware.org (Postfix) with ESMTPS id DDADB3945C1F
 for <gdb-patches@sourceware.org>; Fri,  1 Apr 2022 12:50:38 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org DDADB3945C1F
Received: from [2001:470:142:3::e] (port=51574 helo=fencepost.gnu.org)
 by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.90_1) (envelope-from <eliz@gnu.org>)
 id 1naGjd-0001cM-Dj; Fri, 01 Apr 2022 08:50:37 -0400
Received: from [87.69.77.57] (port=4540 helo=home-c4e4a596f7)
 by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.90_1) (envelope-from <eliz@gnu.org>)
 id 1naGjS-0003Iv-Lc; Fri, 01 Apr 2022 08:50:36 -0400
Date: Fri, 01 Apr 2022 15:50:38 +0300
Message-Id: <838rsp55nl.fsf@gnu.org>
From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: aburgess@redhat.com, pedro@palves.net, gdb-patches@sourceware.org
In-Reply-To: <Ykbx0M07yEdf2/b+@adacore.com> (message from Joel Brobecker on
 Fri, 1 Apr 2022 05:36:32 -0700)
Subject: Re: GDB 12.0.90 available for testing
References: <20220320055815.2A90FA4D6C@takamaka.home> <83sfr4a93r.fsf@gnu.org>
 <83pmm8a7gn.fsf@gnu.org> <83o81sa6nu.fsf@gnu.org>
 <83ilrzap07.fsf@gnu.org> <83mth67i8m.fsf@gnu.org>
 <72ad3448-0ff0-f36c-d1f3-cc194c0503b8@palves.net>
 <83ee2i72vl.fsf@gnu.org> <87sfqx864d.fsf@redhat.com>
 <83fsmx59wi.fsf@gnu.org> <Ykbx0M07yEdf2/b+@adacore.com>
X-Spam-Status: No, score=1.7 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH,
 DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF,
 RCVD_IN_BARRACUDACENTRAL, SPF_HELO_PASS, SPF_PASS, TXREP,
 T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.4
X-Spam-Level: *
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 <gdb-patches.sourceware.org>
List-Unsubscribe: <https://sourceware.org/mailman/options/gdb-patches>,
 <mailto:gdb-patches-request@sourceware.org?subject=unsubscribe>
List-Archive: <https://sourceware.org/pipermail/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-request@sourceware.org?subject=help>
List-Subscribe: <https://sourceware.org/mailman/listinfo/gdb-patches>,
 <mailto:gdb-patches-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Apr 2022 12:50:40 -0000

> Date: Fri, 1 Apr 2022 05:36:32 -0700
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: Andrew Burgess <aburgess@redhat.com>, pedro@palves.net,
> 	gdb-patches@sourceware.org, brobecker@adacore.com
> 
> > P.S. Aren't these problems visible in the MinGW64 builds of GDB 12?
> > IOW, is this only a problem with the MinGW flavor I'm using to build
> > GDB?
> 
> We test that configuration every night, and I confirm we haven't seen
> that issue.

With -i=mi or with the CLI?  The latter doesn't show any problems
here.

Do you also use GDB via Emacs's "M-x gdb" command (which invokes GDB
with -i=mi) or with "M-x gud-gdb" (which uses the CLI and
annotations)?

If this problem only happens with mingw.org's MinGW, I'm okay with
having local workarounds.  Although I'm puzzled how can that be, since
both MinGW flavors are supposed to share the same runtime.  Or do you
build GDB against the UCRT (as opposed to MSVCRT) runtime?