This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug nptl/18435] pthread_once hangs when init routine throws an exception
- From: "joseph at codesourcery dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Wed, 20 May 2015 16:56:42 +0000
- Subject: [Bug nptl/18435] pthread_once hangs when init routine throws an exception
- Auto-submitted: auto-generated
- References: <bug-18435-131 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=18435
--- Comment #4 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
On Wed, 20 May 2015, msebor at redhat dot com wrote:
> Thanks for the reference to the POSIX issue. I admit I was initially also
> skeptical that this use case was intended to be supported by POSIX but became
> convinced after reading the following quotes from the spec:
>
> http://permalink.gmane.org/gmane.comp.lib.boost.devel/128855
>
> It seems clear that POSIX not only intends to support such a use case (of
> pthread_cleanup_push/pop) but even encourages exception-aware implementations
> (referring to them as "the ideal solution").
You should be skeptical that wording inherited more or less unchanged from
the rationale in the 1995/6 edition of POSIX.1 is particularly relevant to
what's ideal in 2015, especially given that the then-anticipated rework of
POSIX into a language-independent specification with separate C language
bindings never materialized.
--
You are receiving this mail because:
You are on the CC list for the bug.