From: Pedro Alves <pedro@palves.net>
To: Adrian Oltean <adrian.oltean@nxp.com>,
Luis Machado <luis.machado@arm.com>, Eli Zaretskii <eliz@gnu.org>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: [EXT] Re: Slow "symbol-file" when using GDB 12.1 on Windows hosts
Date: Tue, 4 Apr 2023 15:17:29 +0100 [thread overview]
Message-ID: <e2fe7ec6-ccea-6671-8f86-f947a0417c46@palves.net> (raw)
In-Reply-To: <AM6PR04MB463051BCB46635A68C964DEBF1939@AM6PR04MB4630.eurprd04.prod.outlook.com>
On 2023-04-04 3:07 p.m., Adrian Oltean wrote:
> GDB 12:
> (gdb) show version
> GNU gdb (Arm GNU Toolchain 12.2.Rel1 (Build arm-12.24)) 12.1.90.20221210-git
> (gdb) show configuration
> This GDB was configured as follows:
...
> --with-separate-debug-dir=//lib/debug (relocatable)
^^^^^^^^^^^
>
There you go, it's right there.
> GDB 10:
> (gdb) show version
> GNU gdb (GNU Arm Embedded Toolchain 10.3-2021.10) 10.2.90.20210621-git
> (gdb) show configuration
> This GDB was configured as follows:
...
> --with-separate-debug-dir=/mnt/workspace/workspace/GCC-10-pipeline/jenkins-GCC-10-pipeline-338_20211018_1634516203/install-mingw/lib/debug (relocatable)
...
> Is the described behavior specific to the Windows image I have? Maybe... I don't know...
Looks like your GDB 12 was configured to look into that network path for separate debug files.
> But it's a fact that the default 'debug-file-directory' that's configured in GDB 12 introduces some
> unwanted side effects for me. If I 'set debug-file-directory' before issuing a 'symbol-file',
> everything's fine.
The next question would be whether "--with-separate-debug-dir=//lib/debug" would be the default
on Windows GDB 12 for some reason, of whether it was explicitly specified in that build. I would
hazard a guess that it's the latter, but you never know.
prev parent reply other threads:[~2023-04-04 14:17 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
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 [this message]
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=e2fe7ec6-ccea-6671-8f86-f947a0417c46@palves.net \
--to=pedro@palves.net \
--cc=adrian.oltean@nxp.com \
--cc=eliz@gnu.org \
--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).