This is the mail archive of the
mailing list for the Cygwin project.
Re: Question of the necessity of rebaseall
-----BEGIN PGP SIGNED MESSAGE-----
According to Lenik on 5/13/2009 7:49 PM:
>> You have it backwards. Forking doesn't break the relocation. Relocation
>> breaks forking. cygwin1.dll needs to have a very special memory layout to
>> implement the fork semantics in Win32. If this memory layout is
>> disrupted, fork breaks.
> Could you explain in more detail? I can't find any document about this
> special memory layout.
Read the source. This link is a bit old, but still captures the essence:
Remember, the semantics of fork is that BOTH processes (the parent and
child) must see the SAME memory, and that includes all shared libraries
being mapped at the SAME location. But since Windows doesn't provide a
native fork, the child must remap everything that the parent had, and hope
that it lands at the same place. Rebasing improves the chance that the
child will remap, because there are fewer dlls to be remapped in an
Don't work too hard, make some time for fun as well!
Eric Blake firstname.lastname@example.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html