This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: GCC and getcwd
- From: "Barubary" <barubary at cox dot net>
- To: <cygwin at cygwin dot com>
- Date: Fri, 1 Feb 2002 04:23:26 -0800
- Subject: Re: GCC and getcwd
- References: <08B08C9FA5EBD311A2CC009027D5BF81032B0F9E@remailnt2-re01.westat.com> <4.3.1.2.20020131175754.02150450@pop.ma.ultranet.com>
> >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/