Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Subject:	Re: Multiple installations and 3PPs
From:	Adrian Cox <adrian AT humboldt DOT co DOT uk>
To:	sailorleo AT isonews2 DOT com
Cc:	Cygwin <cygwin AT cygwin DOT com>
In-Reply-To:	<41E9B859.8040102@isonews2.com>
References:	<1105721403 DOT 28030 DOT 53 DOT camel AT localhost> <20050114171548 DOT GB6227 AT trixie DOT casa DOT cgf DOT cx> <1105726072 DOT 28030 DOT 78 DOT camel AT localhost> <41E9B859 DOT 8040102 AT isonews2 DOT com>
Date:	Sun, 16 Jan 2005 09:11:42 +0000
Message-Id:	<1105866703.28030.83.camel@localhost>
Mime-Version:	1.0
X-IsSubscribed:	yes

On Sat, 2005-01-15 at 19:42 -0500, Arturus Magi wrote:
> Adrian Cox wrote:
> 
>   > So what are the other problems?
> 
> Programs picking up the wrong version of the DLL and failing with little 
> or no explanation available to the user (whom will, likely as not, fail 
> to provide a useful report to the developer, if they bother to report it 
> at all), for one.

I know that with current Cygwin both instances will open the same shared
memory region but expect a different format of the contents. That's why
I proposed making each cygwin1.dll derive the name of the shared memory
region from its native WIN32 path. I'm interested in failures that would
still occur if the two cygwin DLLs used different shared memory regions
and registry keys.

-- 
Adrian Cox <adrian AT humboldt DOT co DOT uk>


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -