From: Tom Tromey <tom@tromey.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: time to release soon? GDB 8.1.1 release 2018-05-14 update
Date: Fri, 18 May 2018 19:50:00 -0000 [thread overview]
Message-ID: <87zi0wg3ts.fsf@tromey.com> (raw)
In-Reply-To: <20180518190017.7drpbrzmfg5h76pt@adacore.com> (Joel Brobecker's message of "Fri, 18 May 2018 12:00:17 -0700")
>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:
>> If the DWARF reader patch goes in 8.1, then I will do that.
>> Otherwise I probably won't. I'm not very concerned about -readnow; I
>> think pretty much only gdb developers use it or should use it.
Joel> OK with me. But wouldn't the issue surface as well without -readnow,
Joel> when expanding the partial symtab?
In theory it shouldn't.
The way this works is that psymtab.c:psymtab_to_symtab, and other such
functions, should not try to expand a psymtab coming from a partial CU
(that both of these things are called "partial" is unfortunate).
Instead, these functions find the canonical user and expand that
instead, like:
/* If it is a shared psymtab, find an unshared psymtab that includes
it. Any such psymtab will do. */
while (pst->user != NULL)
pst = pst->user;
-readnow wasn't obeying this rule. The fix isn't in psymtab.c, though,
because dwarf2read plays a little game to pretend that it is using the
index with -readnow, because in this mode there's no reason to make a
psymtab at all.
Maybe should still patch psym_expand_all_symtabs, but only DWARF is
using this feature, so there didn't seem to be a reason.
Joel> Regarding the DWARF reader patch, I'd say we put it in 8.1.1.
Ok, I will backport it next week.
Tom
prev parent reply other threads:[~2018-05-18 19:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 17:59 Joel Brobecker
2018-05-17 16:19 ` Tom Tromey
2018-05-17 20:37 ` Joel Brobecker
2018-05-18 0:32 ` Tom Tromey
2018-05-18 19:14 ` Joel Brobecker
2018-05-18 19:50 ` 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=87zi0wg3ts.fsf@tromey.com \
--to=tom@tromey.com \
--cc=brobecker@adacore.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