Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-ID:	<00b301c1ab1b$40277940$a7eb0544@CX535256D>
From:	"Barubary" <barubary AT cox DOT net>
To:	<cygwin AT cygwin DOT com>
References:	<08B08C9FA5EBD311A2CC009027D5BF81032B0F9E AT remailnt2-re01 DOT westat DOT com> <4 DOT 3 DOT 1 DOT 2 DOT 20020131175754 DOT 02150450 AT pop DOT ma DOT ultranet DOT com>
Subject:	Re: GCC and getcwd
Date:	Fri, 1 Feb 2002 04:23:26 -0800
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2600.0000

> >This is not the Unix way to do things. The Unix API does not provide any
way for a process to find out where its executable image is located (it
might not exist anymore!) See:
> >http://www.erlenstar.demon.co.uk/unix/faq_2.html#SEC23

This isn't the Windows NT way to do things, either.  Processes only in name
have an EXE associated with them.  It is the fact that kernel32.dll's
CreateProcessW implements process creation by using memory-mapped files with
the EXE that associates an EXE filename with a process (and locks the EXE
file against writing or deleting).

-- Barubary


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -