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

[Svante Signell]

On Fri, 2017-09-08 at 00:39 +0200, Samuel Thibault wrote:

> 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)
> case.

Sorry, but none of these changes had any effect. I built a new libc.so including
print statements and run the programs with both LD_PRELOAD and LD_LIBRARY_PATH.
No difference.