From: Eli Zaretskii <eliz@gnu.org>
To: Adrian Oltean <adrian.oltean@nxp.com>
Cc: luis.machado@arm.com, gdb@sourceware.org
Subject: Re: [EXT] Re: Slow "symbol-file" when using GDB 12.1 on Windows hosts
Date: Mon, 20 Mar 2023 15:58:25 +0200 [thread overview]
Message-ID: <838rfr8qym.fsf@gnu.org> (raw)
In-Reply-To: <AM6PR04MB4630F94FF5442C662C5121F0F1809@AM6PR04MB4630.eurprd04.prod.outlook.com> (message from Adrian Oltean on Mon, 20 Mar 2023 13:33:49 +0000)
> From: Adrian Oltean <adrian.oltean@nxp.com>
> CC: "luis.machado@arm.com" <luis.machado@arm.com>, "gdb@sourceware.org"
> <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.
next prev parent reply other threads:[~2023-03-20 13:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 15:50 Adrian Oltean
2023-03-17 17:29 ` Luis Machado
2023-03-17 18:49 ` Eli Zaretskii
2023-03-17 19:02 ` Luis Machado
2023-03-20 12:29 ` Adrian Oltean
2023-03-20 13:19 ` Eli Zaretskii
2023-03-20 13:27 ` [EXT] " Adrian Oltean
2023-03-20 13:33 ` Adrian Oltean
2023-03-20 13:58 ` Eli Zaretskii [this message]
2023-03-22 14:30 ` Luis Machado
2023-04-03 16:48 ` Adrian Oltean
2023-04-04 12:53 ` Pedro Alves
2023-04-04 13:02 ` Luis Machado
2023-04-04 14:07 ` Adrian Oltean
2023-04-04 14:15 ` Luis Machado
2023-04-04 14:17 ` Pedro Alves
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=838rfr8qym.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=adrian.oltean@nxp.com \
--cc=gdb@sourceware.org \
--cc=luis.machado@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).