Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-developers-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com
Date: Wed, 26 Jan 2000 10:40:06 -0500
From: Chris Faylor <cgf AT cygnus DOT com>
To: Mumit Khan <khan AT NanoTech DOT Wisc DOT EDU>
Cc: cygwin-developers AT sourceware DOT cygnus DOT com
Subject: Re: Trapping the Win32 API path functions
Message-ID: <20000126104006.B1047@cygnus.com>
Mail-Followup-To: Mumit Khan <khan AT NanoTech DOT Wisc DOT EDU>,
	cygwin-developers AT sourceware DOT cygnus DOT com
References: <20000124220247 DOT A5855 AT cygnus DOT com> <Pine DOT HPP DOT 3 DOT 96 DOT 1000125225735 DOT 7124F-100000 AT hp2 DOT xraylith DOT wisc DOT edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <Pine.HPP.3.96.1000125225735.7124F-100000@hp2.xraylith.wisc.edu>; from khan@NanoTech.Wisc.EDU on Tue, Jan 25, 2000 at 11:10:01PM -0600

On Tue, Jan 25, 2000 at 11:10:01PM -0600, Mumit Khan wrote:
>On Mon, 24 Jan 2000, Chris Faylor wrote:
>
>> It has occurred to me that we could trap the Win32 functions
>> which understand paths and slip Cygwin style paths in there.
>> 
>> At the most trivial, we could make a front-end for kernel32.dll
>> although I'm sure it wouldn't be that easy.
>
>Hmmm ... I'm trying to understand this. I can see hooking/replacing
>selected kernel32 functions in Cygwin DLL and doing pre- and post-
>processing before- and after- the real call.
>
>Are you suggesting that you make a replacement for kernel32? Could
>you elaborate a bit on your proposal please?

It is theoretically possible to trap all calls to a DLL.  I've seen
numerous references to it on DejaNews but I've never tried it myself.

I was proposing doing this in such a way that functions like CreateFile
would appear to accept cygwin paths.

cgf