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: [committed][gdb/symtab] Fix data race in ~charset_vector
Date: Fri, 15 Jul 2022 08:34:51 -0600 [thread overview]
Message-ID: <871qumsaus.fsf@tromey.com> (raw)
In-Reply-To: <1d267cea-387f-f2de-ed72-b6020b80bb4e@suse.de> (Tom de Vries via Gdb-patches's message of "Thu, 14 Jul 2022 20:43:32 +0200")
Tom> Well, the worker threads are detached, so they run until process
Tom> exit. We can not detach them, and do a join, but that postpones
Tom> process exit.
Yeah, we probably don't want to do that.
Tom> This was sofar the only case I found of this type of race, so I
Tom> thought it reasonable to fix like this. If there are more cases, that
Tom> might not be practical.
Makes sense to me.
Tom
prev parent reply other threads:[~2022-07-15 14:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 6:19 Tom de Vries
2022-07-14 17:31 ` Tom Tromey
2022-07-14 18:43 ` Tom de Vries
2022-07-15 14:34 ` 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=871qumsaus.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).