|
From: | Christian Grothoff |
Subject: | Re: GNUnet News: vfork and the signal race |
Date: | Sat, 26 Nov 2011 01:09:59 +0100 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20111004 Lightning/1.0b1 Icedove/3.0.11 |
On 11/25/2011 07:50 PM, Thomas Bushnell, BSG wrote:
Programs which depend on the special suspend-the-parent behavior of vfork were always regarded as buggy...
So relying on the well-documented behavior of a system call is a bug? Did you even read about the scenario I described at https://gnunet.org/vfork ? Before writing this, I looked around for existing information on vfork, but I didn't find anyone making a good argument (or even the claim) that relying on 'suspend-the-parent' was per-se buggy. (Naturally, the result would be non-portable for systems where fork==vfork, but then maybe implementing vfork as fork is the bug? ;-))
Happy hacking Christian
[Prev in Thread] | Current Thread | [Next in Thread] |