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

2017-09-15 Thread Svante Signell
On Fri, 2017-09-15 at 01:49 +0200, Samuel Thibault wrote: > Well, rather avoid having a 'filename' variable along the 'file_name' > variable, that's confusing :) > > Better calling absolute_path for instance. I named it abs_path. > > ++  file_t file = __file_name_lookup (filename, O_EXEC, 0); >

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

2017-09-15 Thread Samuel Thibault
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

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

2017-09-15 Thread Svante Signell
On Fri, 2017-09-15 at 13:20 +0200, Samuel Thibault wrote: > Hello, > > Svante Signell, on ven. 15 sept. 2017 12:35:56 +0200, wrote: > > > > ++  file_t file = __file_name_lookup (filename, O_EXEC, 0); > Still, the question becomes: better use file_name instead of > abs_path, because file_name will