Mailing-List:	contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender:	cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin-developers AT sourceware DOT cygnus DOT com
Date:	Sun, 27 Jun 1999 23:15:54 -0400
From:	Chris Faylor <cgf AT cygnus DOT com>
To:	DJ Delorie <dj AT delorie DOT com>
Cc:	khan AT xraylith DOT wisc DOT EDU, cygwin-developers AT sourceware DOT cygnus DOT com
Subject:	Re: running two independent Cygwin DLLs?
Message-ID:	<19990627231554.A8977@cygnus.com>
References:	<199906280258 DOT VAA23658 AT mercury DOT xraylith DOT wisc DOT edu> <199906280305 DOT XAA00938 AT envy DOT delorie DOT com> <19990627231051 DOT B8904 AT cygnus DOT com> <199906280312 DOT XAA00996 AT envy DOT delorie DOT com>
Mime-Version:	1.0
X-Mailer:	Mutt 0.95.3i
In-Reply-To:	<199906280312.XAA00996@envy.delorie.com>; from DJ Delorie on Sun, Jun 27, 1999 at 11:12:03PM -0400

On Sun, Jun 27, 1999 at 11:12:03PM -0400, DJ Delorie wrote:
>> Actually, all you have to do is "configure --enable-debugging".  That
>> will cause the shared memory regions to be named based on the date/time.
>
>What about the mount tables, though?  Depending on *what* you're
>experimenting with, you may still need to isolate other parts of the
>dll's shared resources.

The mount info is stored in the shared memory region.  Using
--enable-debugging should isolate everything since it affects the base
name that is used to generate shared resources.

cgf

- Raw text -