[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <cd69141c-ecd9-452e-a65a-d8632ed9609c@app.fastmail.com>
Date: Wed, 24 Jul 2024 17:00:13 -0400
From: "Zack Weinberg" <zack@...folio.org>
To: "Rich Felker" <dalias@...c.org>, libc-coord@...ts.openwall.com
Cc: musl@...ts.openwall.com,
"GNU libc development" <libc-alpha@...rceware.org>
Subject: Re: Making exit actually thread-safe
On Wed, Jul 24, 2024, at 3:09 PM, Rich Felker wrote:
There is a clear unique
> reasonable behavior for this situation: any remaining callers block
> until the first call to exit has finished, at which point they no
> longer exist. Leaving exit via longjmp, exceptions, etc. is undefined.
I support this change.
The specification text should probably say explicitly that the exit status of the process is the value passed to the first call to exit, unless an atexit handler calls _exit etc.
zw
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
