Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <00b301c1ab1b$40277940$a7eb0544@CX535256D> From: "Barubary" To: References: <08B08C9FA5EBD311A2CC009027D5BF81032B0F9E@remailnt2-re01.westat.com> <4.3.1.2.20020131175754.02150450@pop.ma.ultranet.com> Subject: Re: GCC and getcwd Date: Fri, 1 Feb 2002 04:23:26 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit 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/