Observation for ALL maintainers who provide dlls (was Re:question for perl maintainer)

Dave Korn dave.korn@artimi.com
Tue Jul 12 09:25:00 GMT 2005

----Original Message----
>From: Christopher Faylor
>Sent: 12 July 2005 04:48

> On Mon, Jul 11, 2005 at 08:33:15PM -0700, Brian Dessent wrote:
>> "Pierre A. Humblet" wrote:
>>> The attached script takes the name of a .exe or .dll,
>>> uses cygcheck to find the dll dependence and checks for conflicts.
>>> This will allow you to check your favorite applications or dlls,
>>> seeing if --enable-auto-image-base works for you.
>> I was under the impression that relocations at startup-time (i.e. all
>> DLL base addresses set to 0x10000000) was fine and doesn't cause the
>> remap issue, since the windows loader apparently will always choose the
>> same layout for the DLLs for a given .exe every time.
> Relocations of standard "statically loaded" dlls can fail on fork the
> same way that dynamically loaded dlls do.  Windows doesn't guarantee
> that the base address will be the same in the "forker" and "forkee" and
> it seems like something in the forked process throws off windows so that
> it chooses a different location for some dlls.

  Maybe we could mitigate a good deal of the trouble by getting setup to add
cygwin1.dll to the systemwide list of KnownDlls?

  On the downside that would mean we had to install it to

Can't think of a witty .sigline today....

More information about the Cygwin-apps mailing list