From: Tom Tromey <tom@tromey.com>
To: Christian Biesinger <cbiesinger@google.com>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Shrink size of dwarf2_per_cu_data
Date: Fri, 23 Apr 2021 06:55:55 -0600 [thread overview]
Message-ID: <87czul88is.fsf@tromey.com> (raw)
In-Reply-To: <CAPTJ0XGKL1qUP_NNDzgcsy3yNpzPjr6f=18sMrDeaQNJEDkV=w@mail.gmail.com> (Christian Biesinger's message of "Thu, 22 Apr 2021 16:39:22 -0500")
Christian> I'm not sure if all the .so files get loaded at the same time, so it
Christian> may be a bit fewer in practice. Of course this does not include any
Christian> CUs that may come from debug symbols for system libraries. Is there a
Christian> gdb command that could tell me the exact number?
I don't think so.
(gdb) pipe maint print stat | grep "psym tables"
is pretty close, but claims to omit expanded CUs.
Also if you're using an index you need something more like
(gdb) pipe maint print stat | egrep "(psym tables|read CUs)"
... then add up both the read and unread CUs.
Tom
prev parent reply other threads:[~2021-04-23 12:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 22:13 Tom Tromey
2020-11-04 10:59 ` Gary Benson via Gdb-patches
2021-04-21 23:04 ` Tom Tromey
2021-04-22 21:39 ` Christian Biesinger via Gdb-patches
2021-04-23 12:55 ` Tom Tromey [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=87czul88is.fsf@tromey.com \
--to=tom@tromey.com \
--cc=cbiesinger@google.com \
--cc=gdb-patches@sourceware.org \
/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