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:16:08 -0400
Message-Id: <199906280316.XAA01031@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: cgf AT cygnus DOT com
CC: khan AT xraylith DOT wisc DOT EDU, cygwin-developers AT sourceware DOT cygnus DOT com
In-reply-to: <19990627231554.A8977@cygnus.com> (message from Chris Faylor on
	Sun, 27 Jun 1999 23:15:54 -0400)
Subject: Re: running two independent Cygwin DLLs?
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> <19990627231554 DOT A8977 AT cygnus DOT com>


> 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.

I was thinking of the permanent table, in the registry.  If you want
to play with the mount API you'd want to use a separate registry key
as well.