From: Tom Tromey <tromey@adacore.com>
To: Jon Turney <jon.turney@dronecode.org.uk>
Cc: Tom Tromey <tromey@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 2/2] Implement target async for Windows
Date: Thu, 17 Nov 2022 11:38:22 -0700 [thread overview]
Message-ID: <87tu2xs9y9.fsf@tromey.com> (raw)
In-Reply-To: <c8475e99-8584-f614-5532-97379b851b95@dronecode.org.uk> (Jon Turney's message of "Thu, 17 Nov 2022 14:33:21 +0000")
>>>>> "Jon" == Jon Turney <jon.turney@dronecode.org.uk> writes:
Jon> Using the language of the standard, the cause would probably be better
Jon> described as "unordered dynamic initialization of non-local variables
Jon> with static storage duration" or something like that.
The normal name in the C++ community is the "static initialization order
fiasco":
https://en.cppreference.com/w/cpp/language/siof
Jon> Yes, that fixes the crash, also.
Jon> Please apply, if you are happy with it.
I'll check it in shortly. Thanks for trying it.
Tom
next prev parent reply other threads:[~2022-11-17 18:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 13:08 [PATCH 0/2] " Tom Tromey
2022-08-03 13:08 ` [PATCH 1/2] Move some Windows operations to worker thread Tom Tromey
2022-08-03 13:33 ` Eli Zaretskii
2022-08-03 18:47 ` Tom Tromey
2022-08-03 19:16 ` Eli Zaretskii
2022-08-03 13:08 ` [PATCH 2/2] Implement target async for Windows Tom Tromey
2022-11-04 14:28 ` Jon Turney
2022-11-08 18:38 ` Tom Tromey
2022-11-13 14:45 ` Jon Turney
2022-11-04 14:59 ` Jon Turney
2022-11-08 18:52 ` Tom Tromey
2022-11-17 14:33 ` Jon Turney
2022-11-17 18:38 ` Tom Tromey [this message]
2022-11-17 18:43 ` Tom Tromey
2022-08-03 13:34 ` [PATCH 0/2] " Eli Zaretskii
2022-08-03 18:54 ` Tom Tromey
2022-08-03 19:17 ` Eli Zaretskii
2022-08-22 18:03 ` 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=87tu2xs9y9.fsf@tromey.com \
--to=tromey@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jon.turney@dronecode.org.uk \
/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).