From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id gLkMBZdmGGQJABUAWB0awg (envelope-from ) for ; Mon, 20 Mar 2023 09:58:47 -0400 Received: by simark.ca (Postfix, from userid 112) id 109F51E223; Mon, 20 Mar 2023 09:58:47 -0400 (EDT) Authentication-Results: simark.ca; dkim=pass (1024-bit key; secure) header.d=sourceware.org header.i=@sourceware.org header.a=rsa-sha256 header.s=default header.b=e01XH9qi; dkim-atps=neutral X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-7.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI, RDNS_DYNAMIC,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 Received: from sourceware.org (ip-8-43-85-97.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id B59551E0D3 for ; Mon, 20 Mar 2023 09:58:46 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 41A8038515D0 for ; Mon, 20 Mar 2023 13:58:46 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 41A8038515D0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1679320726; bh=txJOlGdqAZM7Nh46a7DMBx0wV7WkEvufKavwxmUc7Po=; h=Date:To:Cc:In-Reply-To:Subject:References:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From:Reply-To:From; b=e01XH9qiQ5Y8TcFs2gWJ5TSLd7kr8Z57eqL4qjHnPn6YGwzwt86u8aAzuAnc4HEAe W2OMaiz5AOsnzgia40Oul+f71AKlIcsIH91O0Ky3p0+jKFDqTKaCge3ZC9QYZs3BGX TEL18g0fcySW9TlbDl/Q/kOZTjahpMQPSjKopC8Q= Received: from eggs.gnu.org (eggs.gnu.org [IPv6:2001:470:142:3::10]) by sourceware.org (Postfix) with ESMTPS id 66E823858413 for ; Mon, 20 Mar 2023 13:58:20 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 66E823858413 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 1peG1j-0008ML-2k; Mon, 20 Mar 2023 09:58:19 -0400 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 1peG1h-00069S-Mx; Mon, 20 Mar 2023 09:58:18 -0400 Date: Mon, 20 Mar 2023 15:58:25 +0200 Message-Id: <838rfr8qym.fsf@gnu.org> To: Adrian Oltean Cc: luis.machado@arm.com, gdb@sourceware.org In-Reply-To: (message from Adrian Oltean on Mon, 20 Mar 2023 13:33:49 +0000) Subject: Re: [EXT] Re: Slow "symbol-file" when using GDB 12.1 on Windows hosts References: <070fbd13-e03c-a4e8-1372-3f7813b7db92@arm.com> <83sfe3ciwy.fsf@gnu.org> <0df63795-2424-52e0-da93-92ab75a6d50f@arm.com> <83bkkn8sre.fsf@gnu.org> X-BeenThere: gdb@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Eli Zaretskii via Gdb Reply-To: Eli Zaretskii Errors-To: gdb-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb" > From: Adrian Oltean > CC: "luis.machado@arm.com" , "gdb@sourceware.org" > > Date: Mon, 20 Mar 2023 13:33:49 +0000 > > These were the questions: > 1. Is GDB trying to find debug symbols in all those folders? Or what's with them? > 2. What is the code from GDB that artificially builds all those paths? > 3. GDB 10.2 does not seem to access "C:\Windows\CSC\v2.0.6\namespace\lib", nor > "\\lib\debug\Users\MyUsername\...". Is this related to a recent change? Can someone > point to the relevant change in this case? > 4. Is there a command to stop GDB from attempting to access those files/folders? Sorry, I don't know the answers. Maybe Luis or someone else does. In general, AFAIK GDB searches directories recorded in the program's debug info, and also some source directories. See the node "Source Path" in the GDB manual. Also try "show solib-search-path". The "show libthread-db-search-path" command could also be relevant; see "Threads" in the manual.