Re: vfork revisited (was 64bit clean XEmacs)
Glynn Clements writes:
For the benefit of platforms which don't overcommit, it would be
useful to figure out what we call between fork() and exec(), so that
vfork() can be used instead where possible.
An alternate solution is to vfork and immediately exec a small
program that does the dups and fiddling with signals that is
required, and then execs the program that XEmacs really wanted to
exec. On UNIX systems, that small program could probably be
/bin/sh, but we could write one easily enough.