[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: |
Mon, 25 Sep 2017 18:01:48 +0200 |
User-agent: |
NeoMutt/20170113 (1.7.2) |
Svante Signell, on lun. 25 sept. 2017 17:51:52 +0200, wrote:
> However child_lookup() expects a const char *, but the compiler does not
> complain here.
Sure, you can pass a char* to a function that expects a const char*.
> The following tests still reveal unwanted behaviour: (where to change ?) I
> have
> not tested any new scripts.
It's in the PATH lookup case, just below where you added your code. It
indeed have to cope with the case where elements in $PATH are relative
paths (even if that's really not good practice to have e.g. "." in one's
own $PATH)
Samuel
- Re: BUG: /proc/self/exe reports relative paths, should always return absolute paths?, (continued)
- 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
- Re: BUG: /proc/self/exe reports relative paths, should always return absolute paths?, Svante Signell, 2017/09/22
- Re: BUG: /proc/self/exe reports relative paths, should always return absolute paths?, Samuel Thibault, 2017/09/22
- Re: BUG: /proc/self/exe reports relative paths, should always return absolute paths?, Svante Signell, 2017/09/24
- Re: BUG: /proc/self/exe reports relative paths, should always return absolute paths?, Samuel Thibault, 2017/09/24
- Re: BUG: /proc/self/exe reports relative paths, should always return absolute paths?, Svante Signell, 2017/09/24
- Re: BUG: /proc/self/exe reports relative paths, should always return absolute paths?, Svante Signell, 2017/09/25
- 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/26
- Re: BUG: /proc/self/exe reports relative paths, should always return absolute paths?, Samuel Thibault, 2017/09/26
- Re: BUG: /proc/self/exe reports relative paths, should always return absolute paths?, Svante Signell, 2017/09/26
- Re: BUG: /proc/self/exe reports relative paths, should always return absolute paths?, Samuel Thibault, 2017/09/26
- Re: BUG: /proc/self/exe reports relative paths, should always return absolute paths?, Svante Signell, 2017/09/27
- Re: BUG: /proc/self/exe reports relative paths, should always return absolute paths?, Samuel Thibault, 2017/09/27
- Re: BUG: /proc/self/exe reports relative paths, should always return absolute paths?, Samuel Thibault, 2017/09/27
- Re: BUG: /proc/self/exe reports relative paths, should always return absolute paths?, Svante Signell, 2017/09/27
SIGILL instead of SIGSEGV: Was: Re: BUG: /proc/self/exe reports relative paths, should always return absolute paths?, Svante Signell, 2017/09/11