This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/13845] Infrequent random stop in futex_wait using printf inside alarm signal handler
- From: "ppluzhnikov at google dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: Thu, 15 Mar 2012 15:01:35 +0000
- Subject: [Bug libc/13845] Infrequent random stop in futex_wait using printf inside alarm signal handler
- Auto-submitted: auto-generated
- References: <bug-13845-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=13845
Paul Pluzhnikov <ppluzhnikov at google dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ppluzhnikov at google dot
| |com
--- Comment #5 from Paul Pluzhnikov <ppluzhnikov at google dot com> 2012-03-15 15:01:35 UTC ---
(In reply to comment #4)
> No "Only thread safe functions should be used in the alarm signal handler"
That statement would be incorrect.
The correct statement reads: "only async-signal-safe functions can be used
inside asynchronous signal handler".
http://pubs.opengroup.org/onlinepubs/009695399/functions/xsh_chap02_04.html
This fact is the "ABC" of signal handling, surely *everybody* knows that?
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.