From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pl1-x62b.google.com (mail-pl1-x62b.google.com [IPv6:2607:f8b0:4864:20::62b]) by sourceware.org (Postfix) with ESMTPS id 69CE13858427 for ; Fri, 1 Apr 2022 14:31:15 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 69CE13858427 Received: by mail-pl1-x62b.google.com with SMTP id m18so2608623plx.3 for ; Fri, 01 Apr 2022 07:31:15 -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=IHaEivzrltrrgGMlCBOKhSw+JqwziASQ9nyNHajgE+k=; b=PD4TKxTs7jTT6JPDdlBqNrMLg97T3DRPBJziLQBqjBD7GrT8rHebyYIpXd+oGfKfzf y8ae8Xq5k6PZZ2LxezVEHJqhFpNd2dO9ncODEuGZ/T2i5xEU4q8aDelGcd7aHCyse+0k /7KiFPAufOgJQuQfU0H78PJmVG3BTSH7YCEh6wuJO/B4XTXxcIcc2axJjS+d/QHFf6Cy ebMv5gttPRcv4U5y/zqMC0LNwTg5J+4S5kVFeD96aLoYaXRarbbCNR7RN0Bb16DIIEkY /paxWQumyZm+mnteDhU0ZELqvtiXk8uGq3837ja4xBQ0fJNV1vNG02ISHwrGArs8UEXJ e0lg== X-Gm-Message-State: AOAM531Ax9X21oF+oyUawNn3YMwdbuM7HG/YCA132xc/579didv1Ns/q cNe6fZISp8lQiuwrvQ0vzT6d X-Google-Smtp-Source: ABdhPJxgXusRh0KihX/Qzi1ba6a291QaYCQCz+0Z6RRdUQnzFu6RYWQwdrpbl+mjb4Yk3r4p3GuuJA== X-Received: by 2002:a17:902:bf04:b0:149:c5a5:5323 with SMTP id bi4-20020a170902bf0400b00149c5a55323mr10601396plb.97.1648823474302; Fri, 01 Apr 2022 07:31:14 -0700 (PDT) Received: from takamaka.home ([184.69.131.86]) by smtp.gmail.com with ESMTPSA id c21-20020a637255000000b003822e80f132sm2589254pgn.12.2022.04.01.07.31.13 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 01 Apr 2022 07:31:13 -0700 (PDT) Received: by takamaka.home (Postfix, from userid 1000) id C9D1CA58BD; Fri, 1 Apr 2022 07:31:12 -0700 (PDT) Date: Fri, 1 Apr 2022 07:31:12 -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: <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> <8335iw6fr9.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8335iw6fr9.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:31:17 -0000 > > 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? > > It's enough (and simpler) to look at the DLLs on which the GDB > executable on Windows depends, with this command: > > objdump -x gdb.exe | fgrep "DLL Name" Thanks for the tip. Here's what I have: | $ objdump.exe -x gdb.exe | grep "DLL Name" | DLL Name: python39.dll | DLL Name: ADVAPI32.dll | DLL Name: KERNEL32.dll | DLL Name: msvcrt.dll | DLL Name: USER32.dll | DLL Name: WS2_32.dll > Note the two instances of msvcrt.dll -- this is the (traditional) MS C > runtime library. If you see UCRT instead, it might explain the > difference in our observations. No luck with that lead, it seems... -- Joel