From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25379 invoked by alias); 11 Oct 2008 18:47:50 -0000 Received: (qmail 24667 invoked by uid 48); 11 Oct 2008 18:46:36 -0000 Date: Sat, 11 Oct 2008 18:47:00 -0000 Message-ID: <20081011184636.24666.qmail@sourceware.org> From: "morten+sources dot redhat dot com at afdelingp dot dk" To: glibc-bugs@sources.redhat.com In-Reply-To: <20070704013541.4737.nmiell@comcast.net> References: <20070704013541.4737.nmiell@comcast.net> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug libc/4737] fork is not async-signal-safe X-Bugzilla-Reason: CC Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org X-SW-Source: 2008-10/txt/msg00030.txt.bz2 ------- 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.