This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
RE: libiberty/pex-unix vfork abuse?
On 10 December 2007 20:01, Brian Dessent wrote:
> Andreas Schwab wrote:
>
>> Typically in a multithreaded environment vfork is mapped to fork anyway.
>
> ...which is what I don't understand about this whole thread. It seems
> Dave is seeing some strange behavior in Cygwin, but Cygwin's vfork =
> fork, there is no difference. There used to be a vfork specialization
> in Cygwin, but it is broken and has not been enabled in quite a long
> time.
Yes, I've noticed it's #ifdef'd out now I've been through the code more
thoroughly, and it's also the case that in the old version of gcc/libiberty I'm
using the manipulation of the environ variable isn't there either, so I don't
have a current problem to solve myself, but some of the embedded guys might want
to keep an eye out for it.
cheers,
DaveK
--
Can't think of a witty .sigline today....