From: Luis Machado via Gdb <gdb@sourceware.org>
To: Yubin <ablacktshirt@gmail.com>, gdb@sourceware.org
Cc: Tom Tromey <tom@tromey.com>
Subject: Re: parallel loading of debug info in gdb
Date: Tue, 7 Jan 2025 11:07:57 +0000 [thread overview]
Message-ID: <48d24318-27d8-4cae-bfdc-64a8828c6f75@arm.com> (raw)
In-Reply-To: <CAJYFCiN=TGw7So_2mTSJ8G81y1ADTEhK5i1h14hKKOOjmufoRQ@mail.gmail.com>
On 1/7/25 02:14, Yubin via Gdb wrote:
> Hi,
>
> Does gdb supports parallel loading of debug symbols? I am debugging some
> binary which is 3~4GB itself, and loading and parsing its debug info takes
> minutes.
Since a few years, gdb has had worker threads, potentially as many as cores
(physical or virtual) on the system.
So it does support trying to read things in parallel. Unfortunately the
nature of the data limits things somewhat, as you have dependencies and have
to look those up before proceeding further.
I've cc-ed Tromey, which worked in this area before.
>
> Thanks,
> Yubin
next prev parent reply other threads:[~2025-01-07 11:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-07 2:14 Yubin via Gdb
2025-01-07 11:07 ` Luis Machado via Gdb [this message]
2025-01-07 11:33 ` Yubin via Gdb
2025-01-07 23:45 ` Tom Tromey
2025-01-08 15:40 ` Yubin via Gdb
2025-01-09 0:26 ` Tom Tromey
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=48d24318-27d8-4cae-bfdc-64a8828c6f75@arm.com \
--to=gdb@sourceware.org \
--cc=ablacktshirt@gmail.com \
--cc=luis.machado@arm.com \
--cc=tom@tromey.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