From: "Tom Tromey (Code Review)" <gerrit@gnutoolchain-gerrit.osci.io>
To: Christian Biesinger <cbiesinger@google.com>, gdb-patches@sourceware.org
Subject: [review] [RFC] Don't block on finishing demangling msymbols
Date: Thu, 31 Oct 2019 22:42:00 -0000 [thread overview]
Message-ID: <20191031224224.F297C20AF6@gnutoolchain-gerrit.osci.io> (raw)
In-Reply-To: <gerrit.1572481416000.I9d871917459ece0b41d31670b3c56600757aea66@gnutoolchain-gerrit.osci.io>
Tom Tromey has posted comments on this change.
Change URL: https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/463
......................................................................
Patch Set 1:
(1 comment)
https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/463/1/gdb/minsyms.c
File gdb/minsyms.c:
https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/463/1/gdb/minsyms.c@1390
PS1, Line 1390:
1310 | minimal_symbol_reader::install ()
| ...
1385 | m_objfile->per_bfd->msymbols = std::move (msym_holder);
1386 |
1387 | msymbols = m_objfile->per_bfd->msymbols.get ();
1388 | objfile_per_bfd_storage* per_bfd = m_objfile->per_bfd;
1389 |
1390 > m_objfile->per_bfd->m_minsym_future
1391 > = gdb::thread_pool::g_thread_pool->post_task ([msymbols, mcount,
1392 > per_bfd] ()
1393 | {
1394 | #if CXX_STD_THREAD
1395 | /* Mutex that is used when modifying or accessing the demangled
1396 | hash table. */
1397 | std::mutex demangled_mutex;
> I didn't look in detail but the main possible danger here is if
> this needs any information from the minimal symbol reader, then
> it will fail since that goes out of scope.
I forgot, there's actually another danger, which is why I haven't
tried to do background psymtab reading yet.
The problem is that an objfile can possibly have a short lifetime.
So, in theory it could be deleted while the worker threads are
still running.
For psymtabs I am thinking I will convert objfiles to be managed
via shared_ptr<>. However, this patch got a bit bogged down and
so I haven't completed it yet.
--
Gerrit-Project: binutils-gdb
Gerrit-Branch: master
Gerrit-Change-Id: I9d871917459ece0b41d31670b3c56600757aea66
Gerrit-Change-Number: 463
Gerrit-PatchSet: 1
Gerrit-Owner: Christian Biesinger <cbiesinger@google.com>
Gerrit-CC: Tom Tromey <tromey@sourceware.org>
Gerrit-Comment-Date: Thu, 31 Oct 2019 22:42:24 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: Tom Tromey <tromey@sourceware.org>
Gerrit-MessageType: comment
next prev parent reply other threads:[~2019-10-31 22:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-31 0:23 Christian Biesinger (Code Review)
2019-10-31 21:24 ` Tom Tromey (Code Review)
2019-10-31 22:42 ` Tom Tromey (Code Review) [this message]
2019-11-04 5:52 ` Christian Biesinger (Code Review)
2019-11-26 21:50 ` Tom Tromey (Code Review)
2019-11-27 23:07 ` Christian Biesinger (Code Review)
2019-12-13 21:46 ` Tom Tromey (Code Review)
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=20191031224224.F297C20AF6@gnutoolchain-gerrit.osci.io \
--to=gerrit@gnutoolchain-gerrit.osci.io \
--cc=cbiesinger@google.com \
--cc=gdb-patches@sourceware.org \
--cc=gnutoolchain-gerrit@osci.io \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).