This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/4737] fork is not async-signal-safe
- From: "morten+sources dot redhat dot com at afdelingp dot dk" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: 11 Oct 2008 18:46:36 -0000
- Subject: [Bug libc/4737] fork is not async-signal-safe
- References: <20070704013541.4737.nmiell@comcast.net>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From morten+sources dot redhat dot com at afdelingp dot dk 2008-10-11 18:46 -------
Created an attachment (id=2996)
--> (http://sourceware.org/bugzilla/attachment.cgi?id=2996&action=view)
fork-fail.c
Here is another short example which triggers the bug, but without using
malloc().
>From signal(7):
POSIX.1-2003 requires an implementation to guarantee that the following
functions can be safely called inside a signal handler:
...
fork()
...
Are there any plans to fix this issue in glibc?
Best regards,
Morten K. Poulsen
--
http://sourceware.org/bugzilla/show_bug.cgi?id=4737
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.