This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: /proc/<pid>/exe points to void
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Tue, 24 Jan 2006 18:45:28 +0100
- Subject: Re: /proc/<pid>/exe points to void
- References: <uhdjjkyi2.fsf@gnu.org> <20050310220045.GC20798@cygbert.vinschen.de> <u1xamjhtl.fsf@gnu.org> <20050311160956.GB2821@cygbert.vinschen.de> <ufynid99e.fsf@gnu.org>
- Reply-to: cygwin at cygwin dot com
On Jan 20 13:50, Sam Steingold wrote:
> >> > On Mar 10 16:00, Sam Steingold wrote:
> >> >> /proc/<pid>/exe points to "foo", not to "foo.exe", so it cannot be
> >> >> opened &c.
> >> > ^^^^
> >> > ????
> >>
> >> how do I find out which file is running if /proc/<pid>/exe cannot be
> >> opened?
> >
> > access(2) or stat(2)
>
> http://www.opengroup.org/onlinepubs/009695399/functions/access.html
> the above spec of access appears to indicate that if access() succeeds
> then open() must succeed too.
> this is not the case in cygwin: /proc/self/exe cannot be open()ed.
I've just checked in a patch which tacks on the .exe suffix to
/proc/$PID/exe, as well as a patch to realpath which returns the
pathname with .exe suffix, even if the original name has no suffix
given. We will give this a try. Please test the next snapshot.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/