From: Tom Tromey <tom@tromey.com>
To: Tom de Vries <tdevries@suse.de>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH][gdb/symtab] Fix check-psymtab failure for inline function
Date: Tue, 10 Mar 2020 18:08:55 -0600 [thread overview]
Message-ID: <874kuv7nxk.fsf@tromey.com> (raw)
In-Reply-To: <20200309145237.GA20334@delia> (Tom de Vries's message of "Mon, 9 Mar 2020 15:52:39 +0100")
>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:
Tom> When loading the executable in gdb, we create a partial symbol for foo, but
Tom> after expansion into a full symbol table no actual symbol is created,
Tom> resulting in a maint check-psymtab failure:
Tom> ...
Tom> (gdb) maint check-psymtab
Tom> Static symbol `foo' only found in inline.c psymtab
Tom> ...
Tom> Fix this by preventing the creation of this type of partial symbol.
With this patch, if there is a function which is only inlined (there is
no "out-line" copy), will "break function" still work?
It seems to me that it wouldn't always, because there wouldn't be a
partial symbol to match. Maybe it might work accidentally if the inline
function appears in a CU that is already expanded, like main's. So the
test would have to be an always-inline function that isn't used in
main's CU.
If it does work, then I wonder how, since my mental model is that all
the paths to expansion require a matching partial symbol.
If it doesn't work, then I think a different fix is needed.
thanks,
Tom
next prev parent reply other threads:[~2020-03-11 0:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-09 14:52 Tom de Vries
2020-03-11 0:08 ` Tom Tromey [this message]
2020-03-18 13:48 ` [committed][gdb/testsuite] Add test-case gdb.dwarf2/break-inline-psymtab.exp Tom de Vries
2020-04-02 14:24 ` Pedro Alves
2020-04-02 15:14 ` Tom de Vries
2020-03-18 15:58 ` [PATCH][gdb/symtab] Fix check-psymtab failure for inline function Tom de Vries
2020-04-02 8:46 ` [PING][PATCH][gdb/symtab] " Tom de Vries
2020-04-06 20:40 ` [PATCH][gdb/symtab] " 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=874kuv7nxk.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