From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from eggs.gnu.org (eggs.gnu.org [IPv6:2001:470:142:3::10]) by sourceware.org (Postfix) with ESMTPS id A5C6F3858D35 for ; Sat, 7 Jan 2023 14:28:51 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org A5C6F3858D35 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=gnu.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=gnu.org Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pEABm-0000S5-HO; Sat, 07 Jan 2023 09:28:50 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=RTbd3EMMdu1fuhKNOtwrqJ58o/F/ahfbKZP4VeiRWew=; b=lhM/7/FKplRi 8TIeSh0q7bCc9HQF7vmBpwpNlewno/jGxqjJKKGI5Tg/iXhFMKibFKhd5YPTx+hiZb1r/4jiEvqZa hpFW5mHd4lXILGGTNPd/V8YUpHL2riIpoiF1CUiCnE8mQgA1U8+M7jhYcDsBIHDyPWhObhwymjSGZ AhkSal+XvFRBs8v3AyMo2uTTudPr90UhBnnO8MnJv064Hh562K2igvXM4JQedm7CnV3LoUqkF1lly C60GDebcVEp1aVGZKNmCqhxMqBBQ9ciG8eHcaidrYewJoiB1WgP3saKMCGkucNAn/YIZ5lnEqDH+h Sxb1XoMW1MT/5WzeyAIxMg==; Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pEABl-0001dB-VS; Sat, 07 Jan 2023 09:28:50 -0500 Date: Sat, 07 Jan 2023 16:29:09 +0200 Message-Id: <838ries9je.fsf@gnu.org> From: Eli Zaretskii To: Andreas Schwab Cc: gdb-patches@sourceware.org In-Reply-To: <878rieh194.fsf@igel.home> (message from Andreas Schwab on Sat, 07 Jan 2023 15:23:35 +0100) Subject: Re: Two observations using GDB 13 snapshot References: <83h6xugc5v.fsf@gnu.org> <83r0w6uaad.fsf@gnu.org> <87fscmemeo.fsf@linux-m68k.org> <83358mu1tv.fsf@gnu.org> <87bknaek9z.fsf@linux-m68k.org> <83v8lisjlx.fsf@gnu.org> <87lemeh4wz.fsf@igel.home> <83h6x2sb5x.fsf@gnu.org> <87cz7qh2db.fsf@igel.home> <83a62usabj.fsf@gnu.org> <878rieh194.fsf@igel.home> X-Spam-Status: No, score=1.9 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,KAM_SHORT,RCVD_IN_BARRACUDACENTRAL,SPF_HELO_PASS,SPF_PASS,TXREP autolearn=no autolearn_force=no version=3.4.6 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: > From: Andreas Schwab > Cc: gdb-patches@sourceware.org > Date: Sat, 07 Jan 2023 15:23:35 +0100 > > On Jan 07 2023, Eli Zaretskii wrote: > > > GNU gdb ((MinGW32 GDB)) 13.0.50.20221217-git > > Copyright (C) 2022 Free Software Foundation, Inc. > > License GPLv3+: GNU GPL version 3 or later > > This is free software: you are free to change and redistribute it. > > There is NO WARRANTY, to the extent permitted by law. > > Type "show copying" and "show warranty" for details. > > This GDB was configured as "i686-pc-mingw32". > > Type "show configuration" for configuration details. > > For bug reporting instructions, please see: > > . > > Find the GDB manual and other documentation resources online at: > > . > > > > For help, type "help". > > Type "apropos word" to search for commands related to "word"... > > Reading symbols from ./gdb.exe... > > Here you should see a warning: > > warning: File "[...]/gdb-gdb.gdb" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load". > > Does it help to copy gdb.exe to gdb and use that? Probably. I did it the other way around: copied gdb-gdb.gdb to the .libs subdirectory, and now the prompt is the expected (top-gdb). So the problem is that we are now using libtool, and that causes the GDB executable to be in a directory different from where gdb-gdb.gdb is kept. Joel, should the build procedure copy gdb-gdb.gdb to the .libs subdirectory, where the GDB executable now lives? Thanks.