This is the mail archive of the
mailing list for the glibc project.
[Bug libc/13845] Infrequent random stop in futex_wait using printf inside alarm signal handler
- From: "jon at jonshouse dot co.uk" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: Wed, 14 Mar 2012 14:55:11 +0000
- Subject: [Bug libc/13845] Infrequent random stop in futex_wait using printf inside alarm signal handler
- Auto-submitted: auto-generated
- References: <email@example.com/bugzilla/>
--- Comment #4 from Jonathan Andrews <jon at jonshouse dot co.uk> 2012-03-14 14:55:11 UTC ---
(In reply to comment #3)
Ok, I found the reference to the issue in an up to date man page for "signal"
on a Debian box. My older development machine does not mention it, nor does the
man page for alarm I referenced.
"unspecified" is also a pretty vague term.
Lots of nice unsafe examples via google - thanks web ....
"Interactions between alarm() and setitimer() are unspecified"
No "Only thread safe functions should be used in the alarm signal handler"
Its documented with the assumption that somebody has read it in the correct
order, the documentation isn't thread safe itself :-(
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.