From: Tom de Vries <tdevries@suse.de>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH][gdb] Expand symbolless symtabs using maint expand-symtabs
Date: Thu, 2 Apr 2020 10:44:12 +0200 [thread overview]
Message-ID: <c15f3b6c-43e3-709c-349b-b1e8da3ad673@suse.de> (raw)
In-Reply-To: <87eet70z32.fsf@tromey.com>
On 01-04-2020 21:45, Tom Tromey wrote:
>>>>>> "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.
>
Right, but the includer symtab they're pointing towards are also not
expanded.
Concretely, it does matter for dwarf assembly test-cases, in the sense
that this patch allows me to have the symtab effect of setting a
breakpoint in a certain file, without actually setting the breakpoint,
which means there's no need to flesh out the .debug_line section in
detail, or indeed even create the file.
[ I mentioned this patch as a prerequisite for a dwarf assembly
test-case here :
https://sourceware.org/pipermail/gdb-patches/2020-March/167152.html ]
Furthermore, I found this problem originally not with include psymtabs,
but with this type of one-DIE CUs:
...
<0><b>: Abbrev Number: 1 (DW_TAG_compile_unit)
<c> DW_AT_stmt_list : 0x0
<10> DW_AT_low_pc : 0x400430
<18> DW_AT_high_pc : 0x40045b
<20> DW_AT_name : ../sysdeps/x86_64/start.S
<24> DW_AT_comp_dir : /home/abuild/rpmbuild/BUILD/glibc-2.26/csu
<28> DW_AT_producer : GNU AS 2.31.1
<2c> DW_AT_language : 32769 (MIPS assembler)
...
which I get in every exec on openSUSE Leap 15.1.
In that case, the problem means that "maint expand-symtabs" doesn't
expand the symtab, in violation of the "maint expand-symtabs"
documentation, while also being inconsistent with -readnow which does
create a symbolless symtab.
I used the include psymtabs as test-case and running example because it
reproduces on all platforms in a standard test-case.
> 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 can see how that would help with "maint expand-symtabs <file>", but
still "maint expand-symtabs" would not expand the partial symtab for
../sysdeps/x86_64/start.S.
Thanks,
- Tom
> I guess I'm not super fond of turning the reference arguments to
> pointers, unless there's really no other way.
next prev parent reply other threads:[~2020-04-02 8:44 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
2020-04-02 8:44 ` Tom de Vries [this message]
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=c15f3b6c-43e3-709c-349b-b1e8da3ad673@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@sourceware.org \
--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