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

[Samuel Thibault]

Svante Signell, on mer. 20 sept. 2017 08:46:49 +0200, wrote:
> I changed the patch for __execve() to keep file_name if the path is absolute 
> and
> call realpath() for relative paths.

But then if you call a script that looks at $0 from a relative path,
it'll break.

> (I did also a cetcwd() version, but that does not seem to be needed, and using
> realpath() is simpler.)

It's simpler but doesn't work in the case above.

Samuel