From: Tom Tromey <tom@tromey.com>
To: Tom de Vries <tdevries@suse.de>
Cc: gdb-patches@sourceware.org, Tom Tromey <tom@tromey.com>
Subject: Re: [PATCH][gdb] Expand symbolless symtabs using maint expand-symtabs
Date: Wed, 01 Apr 2020 13:45:37 -0600 [thread overview]
Message-ID: <87eet70z32.fsf@tromey.com> (raw)
In-Reply-To: <e6ec33da-fda7-971f-ca35-166f8c97a3bf@suse.de> (Tom de Vries's message of "Mon, 30 Mar 2020 13:09:01 +0200")
>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:
Tom> When trying to expand the partial symtab for hello.h:
Tom> ...
Tom> $ gdb -batch \
Tom> -iex "set language c" \
Tom> a.out \
Tom> -ex "maint expand-symtabs hello.h" \
Tom> -ex "maint info psymtabs"
Tom> ...
Tom> we in fact find that the partial symtab has not been expanded:
Tom> ...
Tom> { psymtab hello.h ((struct partial_symtab *) 0x27cf070)
Tom> readin no
Tom> ...
Does this matter, though?
I thought include psymtabs like these were kind of placeholders.
Tom> Fix this by passing a NULL symbol_matcher and lookup_name to
Tom> expand_symtabs_matching in maintenance_expand_symtabs, and skipping the call
Tom> to recursively_search_psymtabs if symbol_matcher == NULL and
Tom> lookup_name == NULL.
Could this code use map_symtabs_matching_filename instead?
I guess I'm not super fond of turning the reference arguments to
pointers, unless there's really no other way.
Tom
next prev parent reply other threads:[~2020-04-01 19:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-29 16:00 Tom de Vries
2020-03-30 11:09 ` Tom de Vries
2020-04-01 19:45 ` Tom Tromey [this message]
2020-04-02 8:44 ` Tom de Vries
2020-04-14 13:09 ` Tom de Vries
2020-04-16 6:45 ` [committed][gdb/testsuite] Fix maint-expand-symbols-header-file.exp for cc-with-gdb-index Tom de Vries
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=87eet70z32.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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