From: Tom Tromey <tom@tromey.com>
To: Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
Cc: Tom Tromey <tom@tromey.com>, Tom de Vries <tdevries@suse.de>
Subject: Re: [PATCH 2/2] [gdb] Initialize main_thread_id earlier
Date: Wed, 02 Aug 2023 10:55:41 -0600 [thread overview]
Message-ID: <874jlhfkoi.fsf@tromey.com> (raw)
In-Reply-To: <dd673091-7aa8-64b9-6be6-2ec244cb8cca@suse.de> (Tom de Vries via Gdb-patches's message of "Wed, 2 Aug 2023 16:26:01 +0200")
>>>>> "Tom" == Tom de Vries via Gdb-patches <gdb-patches@sourceware.org> writes:
>> I wonder if it's enough to have:
>> static std::thread::id main_thread_id = std::this_thread::get_id ();
Tom> In principle it's enough but it does expose us to the "Static
Tom> Initialization Order Fiasco" [1], so I prefer this solution.
If we think it's safe enough to initialize it on first use, just moving
the definition into is_main_thread is enough to avoid this problem.
Now, in theory it is possible for gdb to start a thread very early and
then have that thread call is_main_thread, setting the global
incorrectly. If we care about that then we need an explicit call to set
it early during startup.
Tom
next prev parent reply other threads:[~2023-08-02 16:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 10:59 [PATCH 1/2] [gdb] Rename variable main_thread to main_thread_id Tom de Vries
2023-07-28 10:59 ` [PATCH 2/2] [gdb] Initialize main_thread_id earlier Tom de Vries
2023-07-28 13:10 ` Tom Tromey
2023-08-02 14:26 ` Tom de Vries
2023-08-02 16:55 ` Tom Tromey [this message]
2023-08-02 18:46 ` Tom de Vries
2023-08-02 20:48 ` Tom Tromey
2023-08-02 21:21 ` Tom de Vries
2023-07-28 15:36 ` Pedro Alves
2023-08-02 14:45 ` Tom de Vries
2023-07-28 13:06 ` [PATCH 1/2] [gdb] Rename variable main_thread to main_thread_id 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=874jlhfkoi.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).