[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) |
Hello,
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 :)
Samuel
- BUG: /proc/self/exe reports relative paths, should always return absolute paths?, Svante Signell, 2017/09/07
- Re: BUG: /proc/self/exe reports relative paths, should always return absolute paths?, Samuel Thibault, 2017/09/07
- Re: BUG: /proc/self/exe reports relative paths, should always return absolute paths?, Svante Signell, 2017/09/09
- Re: BUG: /proc/self/exe reports relative paths, should always return absolute paths?, Samuel Thibault, 2017/09/09
- Re: BUG: /proc/self/exe reports relative paths, should always return absolute paths?, Svante Signell, 2017/09/11
- Re: BUG: /proc/self/exe reports relative paths, should always return absolute paths?, Svante Signell, 2017/09/14
- Re: BUG: /proc/self/exe reports relative paths, should always return absolute paths?, Samuel Thibault, 2017/09/14
- Re: BUG: /proc/self/exe reports relative paths, should always return absolute paths?, Svante Signell, 2017/09/15
- Re: BUG: /proc/self/exe reports relative paths, should always return absolute paths?,
Samuel Thibault <=
- Re: BUG: /proc/self/exe reports relative paths, should always return absolute paths?, Svante Signell, 2017/09/15
- Re: BUG: /proc/self/exe reports relative paths, should always return absolute paths?, Samuel Thibault, 2017/09/17
- Re: BUG: /proc/self/exe reports relative paths, should always return absolute paths?, Svante Signell, 2017/09/18
- Re: BUG: /proc/self/exe reports relative paths, should always return absolute paths?, Samuel Thibault, 2017/09/18
- Re: BUG: /proc/self/exe reports relative paths, should always return absolute paths?, Samuel Thibault, 2017/09/18
- Re: BUG: /proc/self/exe reports relative paths, should always return absolute paths?, Svante Signell, 2017/09/20
- Re: BUG: /proc/self/exe reports relative paths, should always return absolute paths?, Samuel Thibault, 2017/09/20
- Re: BUG: /proc/self/exe reports relative paths, should always return absolute paths?, Svante Signell, 2017/09/21
- Re: BUG: /proc/self/exe reports relative paths, should always return absolute paths?, Svante Signell, 2017/09/21
- Re: BUG: /proc/self/exe reports relative paths, should always return absolute paths?, Samuel Thibault, 2017/09/21