"Chris Morgan" <[EMAIL PROTECTED]> wrote: > Ahh, very cool. Is there anything we can do to keep cygwin from replacing > wines/libc's fork with its own and presumably fix this problem?
I'm afraid it's impossible to replace cygwin's fork by an one from libc. Cygwin makes some assumptions about "environment" where it runs and accordingly patches virtual memory of a newly created process to mimic fork behaviour. -- Dmitry.
