From: Simon Marchi <simark@simark.ca>
To: Christian Biesinger <cbiesinger@google.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Add a comment briefly explaining partial symbols
Date: Wed, 31 Jul 2019 23:59:00 -0000 [thread overview]
Message-ID: <c5c88919-e648-d8e2-35b8-2a59e7fffecb@simark.ca> (raw)
In-Reply-To: <20190731221252.143637-1-cbiesinger@google.com>
On 2019-07-31 6:12 p.m., Christian Biesinger via gdb-patches wrote:
> Based on an explanation by tromey on IRC.
>
> gdb/ChangeLog:
>
> 2019-07-31 Christian Biesinger <cbiesinger@google.com>
>
> * objfiles.h (objfile): Add a comment describing partial symbols.
> ---
> gdb/objfiles.h | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/gdb/objfiles.h b/gdb/objfiles.h
> index a0c106be3d..c7e0be1955 100644
> --- a/gdb/objfiles.h
> +++ b/gdb/objfiles.h
> @@ -382,7 +382,13 @@ private:
> 2. Additional symbol files added by the add-symbol-file command,
> 3. Shared library objfiles, added by ADD_SOLIB, 4. symbol files
> for modules that were loaded when GDB attached to a remote system
> - (see remote-vx.c). */
> + (see remote-vx.c).
> +
> + GDB typically reads symbols twice -- first an initial scan which just
> + reads "partial symbols"; these are partial information for the
> + static/global symbols in a symbol file. When later looking up symbols,
> + objfile->sf->qf->lookup_symbol is used to check if we only have a partial
> + symbol and if so, read and expand the full compunit. */
>
> struct objfile
> {
>
Hi Christian,
Thanks, that LGTM. But please wait a few days before pushing to see if others have things to add.
Simon
next prev parent reply other threads:[~2019-07-31 23:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 22:12 Christian Biesinger via gdb-patches
2019-07-31 23:59 ` Simon Marchi [this message]
2019-08-05 15:37 ` Christian Biesinger via gdb-patches
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=c5c88919-e648-d8e2-35b8-2a59e7fffecb@simark.ca \
--to=simark@simark.ca \
--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