From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20513 invoked by alias); 19 Dec 2014 20:29:24 -0000 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 Received: (qmail 20427 invoked by uid 48); 19 Dec 2014 20:29:19 -0000 From: "sstewartgallus00 at mylangara dot bc.ca" To: glibc-bugs@sourceware.org Subject: [Bug nptl/17214] Expose a clone variant that shares stacks instead of jumping to a new one Date: Fri, 19 Dec 2014 20:29:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: nptl X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sstewartgallus00 at mylangara dot bc.ca X-Bugzilla-Status: NEW X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: security- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-12/txt/msg00168.txt.bz2 https://sourceware.org/bugzilla/show_bug.cgi?id=17214 --- Comment #13 from Steven Stewart-Gallus --- I am well aware of many of the problems of vfork. You are right that a huge problem is that it doesn't work well with certain compiler optimizations (such as done by Clang in particular). I suppose I really should just use vfork with a new stack and avoid one problem of it (although I'm not sure that works as vfork sets all memory except the current stack as read only in the process, maybe some hack where the function would need to jump to the new stack, vfork and then jump back in the child would be needed). As well, I would definitely prefer using posix_spawn over vfork but unfortunately I can't for a few use cases (also the current GLibc implementation of posix_spawn doesn't use the pipe trick to report errors). Also, vfork wasn't eliminated at all and is still around for very good reasons. -- You are receiving this mail because: You are on the CC list for the bug.