[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, 15 Sep 2017 13:20:10 +0200
User-agent: NeoMutt/20170113 (1.7.2)


Svante Signell, on ven. 15 sept. 2017 12:35:56 +0200, wrote:
> > > ++  file_t file = __file_name_lookup (filename, O_EXEC, 0);
> > 
> > Why doing this?
> This is part of the original code. diff of *.diff files confused again?

Ah, indeed, sorry. A diff of diff is not the easiest thing to read
indeed :)

Still, the question becomes: better use file_name instead of abs_path,
because file_name will usually be shorter, and thus faster to lookup
than the abs_path.

> New patch attached. Since diff -u of two *.diff files gives confusing
> results, e.g. fexecve was not touched, I attach also the edited new
> diff file (removed Index and replaced entries with a/ b/). Why is diff
> not creating the right output?

Because it can not divine what you want exactly :)


reply via email to

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