RE: Multiple cygwin.dll's

["Harold Hunt" <huntharo at msu dot edu>]

Rasjid,

Yes, it will still cause a problem.

The problem is not caused by the location from which the DLL was loaded.
Different versions of cygwin1.dll conflict with each other because all
loaded copies of cygwin1.dll must share a memory area to preserve state
information in a manner similar to an operating system kernel.  Different
versions of cygwin1.dll have different interpretations of the structure of
the shared memory region, thus loaded different versions of cygwin1.dll
results in the shared memory becoming corrupted, which generally crashes any
loaded cygwin1.dll and any programs depending on cygwin1.dll.

So, loaded one version of cygwin1.dll from c:\cygwin and the other from
p:\cygwin isn't going to change the situation at all.

Harold

> -----Original Message-----
> From: cygwin-xfree-owner@sources.redhat.com
> [mailto:cygwin-xfree-owner@sources.redhat.com]On Behalf Of Rasjid
> Sent: Thursday, October 11, 2001 9:10 AM
> To: Cygwin-XFree
> Subject: Multiple cygwin.dll's
>
>
> I have seen various posts to the list saying that having multiple
> cygwin.dll's is a bad thing.
>
> Suppose someone has one verion of Cygwin installed locally, and there is
> another (later) version on the network (with XWin.exe).  If the $path
> variable is adjusted in each case, does it all work.
>
> Or are we still at risk of things breaking if they run their local
> cygwin (so the old cygwin.dll is loaded into memory) and they then try
> to run programs on the network (requiring the newer cygwin.dll)?
>
> Cheers,
>
> Rasjid.