From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pj1-x102e.google.com (mail-pj1-x102e.google.com [IPv6:2607:f8b0:4864:20::102e]) by sourceware.org (Postfix) with ESMTPS id D7F273858D28 for ; Fri, 1 Apr 2022 14:12:08 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org D7F273858D28 Received: by mail-pj1-x102e.google.com with SMTP id gp15-20020a17090adf0f00b001c7cd11b0b3so5424972pjb.3 for ; Fri, 01 Apr 2022 07:12:08 -0700 (PDT) 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=4YXgb/Qk8WrgpcHnk/4hfjrtudWdUtffchzJF3ijkpc=; b=HicCf5dw9PQB2i7/VS+QNZlGihRmb2LxCzY3NLw7BBw2loQ7TxfnFFDCrh97253h4x 20AuKomy2Bamb+3ltlXj9wVH6DUBbosMa7d6PYuSH8ewzTy0ZIYtp3vD8frmew0m4ovQ usXIELekn/emEFoMIuo8YPKXQAzsZloaNvS06v0VHsxdrirnL1vB1KOzv2tDzwcmwGPr i2DOTMzZsoB3yDCJEodmmyaBNvLyXHmoEk3XPD4zdFD+z5lYEdO/gylpV8z5Rc/lxO+k aLezFGU1BG+4pVLqUMI8dfdxJFhTPzm0M8B26GRHQVhChTzj8RMIhMkUumY/fG2F0Iki FXiQ== X-Gm-Message-State: AOAM532KclicrVAQZL2QUAjkT8iCri5i0XUAW6LowRoGp+SuhEgcGjEH yD9VOyXE1hJi6OpLCol307O0gTgzrcJa X-Google-Smtp-Source: ABdhPJzSuFvuzTNzEabvEFJAcasUgE9KwxKcrlaA0G13YLwvWb3u/GGoDrmpN2cSod8YRQFHIbaEzA== X-Received: by 2002:a17:902:c949:b0:154:5215:1db1 with SMTP id i9-20020a170902c94900b0015452151db1mr46367652pla.163.1648822327755; Fri, 01 Apr 2022 07:12:07 -0700 (PDT) Received: from takamaka.home ([184.69.131.86]) by smtp.gmail.com with ESMTPSA id n18-20020a056a0007d200b004fdac35672fsm3070146pfu.68.2022.04.01.07.12.06 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 01 Apr 2022 07:12:07 -0700 (PDT) Received: by takamaka.home (Postfix, from userid 1000) id 412A5A58BD; Fri, 1 Apr 2022 07:12:06 -0700 (PDT) Date: Fri, 1 Apr 2022 07:12:06 -0700 From: Joel Brobecker To: Eli Zaretskii Cc: Joel Brobecker , aburgess@redhat.com, pedro@palves.net, gdb-patches@sourceware.org Subject: Re: GDB 12.0.90 available for testing Message-ID: References: <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> <838rsp55nl.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <838rsp55nl.fsf@gnu.org> X-Spam-Status: No, score=-4.3 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, T_SCC_BODY_TEXT_LINE 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: Fri, 01 Apr 2022 14:12:11 -0000 > > > 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. The testing includes both modes. > 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)? We don't. > 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? I don't know how to answer that question. Is that something I can figure out from looking at how we configure the build of MinGW-w64? -- Joel