[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: Sat, 9 Sep 2017 22:04:21 +0200
User-agent: NeoMutt/20170113 (1.7.2)

Svante Signell, on sam. 09 sept. 2017 10:51:36 +0200, wrote:
> 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 
> No difference.

Which programs do you run?

execv/spawn are called from the parent, so the program that needs
LD_LIBRARY_PATH is the parent of the program to be observed in


reply via email to

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