This is the mail archive of the
cygwin-developers@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: New Win98 problem, similar to _unlink problem
- To: cygwin-developers at sourceware dot cygnus dot com
- Subject: Re: New Win98 problem, similar to _unlink problem
- From: Chris Faylor <cgf at cygnus dot com>
- Date: Mon, 20 Mar 2000 14:27:39 -0500
- References: <200003201922.LAA00566@cygnus.com>
- Reply-To: cygwin-developers at sourceware dot cygnus dot com
On Mon, Mar 20, 2000 at 01:19:36PM -0600, Parker, Ron wrote:
>> -----Original Message-----
>> From: Chris Faylor [mailto:cgf@cygnus.com]
>
><snip>
>
>> You're renaming an opened file. AFAIK, that particular problem is
>> insurmountable in Windows.
>
>I do know that under some circumstances in NT it is possible to rename an
>executable while it is running and therefore open and memory mapped. I have
>not yet figured out what flags are used to open a file and still allow it to
>be renamed.
>
>Since the opening of an executable occurs deep within the OS this may be a
>red herring and the file open modes that are used to allow this may not be
>available to an enduser application.
>
>A simple example of this is to create a simple C program, compile and step
>into it in the debugger, then rename the EXE in Windows Explorer. This is
>allowed, but if you attempt to delete the file in Explore, access is denied.
>
>The HandleEx and NTFilMon programs from Sysinternals showed that the
>executable was in fact open while being debugged and renamed.
Ok. I would appreciate it if someone would investigate this and discover
exactly what needs to be done.
cgf