This is the mail archive of the
glibc-bugs@sources.redhat.com
mailing list for the glibc project.
[Bug nptl/378] posix_spawn implementation, use vfork/execve rather than fork/execve for NPTL Linux.
- From: "drepper at redhat dot com" <sourceware-bugzilla at sources dot redhat dot com>
- To: glibc-bugs at sources dot redhat dot com
- Date: 12 Sep 2004 05:56:27 -0000
- Subject: [Bug nptl/378] posix_spawn implementation, use vfork/execve rather than fork/execve for NPTL Linux.
- References: <20040910004801.378.dennis@mds.rmit.edu.au>
- Reply-to: sourceware-bugzilla at sources dot redhat dot com
------- Additional Comments From drepper at redhat dot com 2004-09-12 05:56 -------
It is not possible to just use vfork. The problem are the atfork handlers which
can be registered. In the child process they can modify the address space.
These changes then would be visible in the parent process.
The best one can do is to let the user select this behavior. A new spawn
attribute (along with setter/getter functions) can be created. If the flag is
set in the attribute vfork is used instead of fork. Then it is the programmers
fault if something goes wrong because of the atfork handlers. In fact, we
should just not run the atfork handlers if vfork is used.
--
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
http://sources.redhat.com/bugzilla/show_bug.cgi?id=378
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.