> >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/
