[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: BUG: /proc/self/exe reports relative paths, should always return abs

From: Samuel Thibault
Subject: Re: BUG: /proc/self/exe reports relative paths, should always return absolute paths?
Date: Fri, 8 Sep 2017 00:39:09 +0200
User-agent: NeoMutt/20170113 (1.7.2)


Svante Signell, on jeu. 07 sept. 2017 10:38:19 +0200, wrote:
> When working on porting gccgo to gcc-7, I found out that many test failures 
> are
> due to a bug in Hurd's implementation of /proc/self/exe (and /proc/<pid>/exe):
> The path returned should always be absolute, not relative. 

That goes back to file_exec_file_name provided with a relative path, and not an
absolute path.  That's where it needs fixing.  I guess it could be a
matter of making sysdeps/mach/hurd/execve.c call realpath(), as well as
sysdeps/mach/hurd/spawni.c in the 
if ((xflags & SPAWN_XFLAGS_USE_PATH) == 0 || strchr (file, '/') != NULL)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]