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

2017-09-07 Thread Samuel Thibault
Hello, Svante Signell, on jeu. 07 sept. 2017 10:38:19 +0200, wrote: > When working on porting gccgo to gcc-7, I found out that many test failures > are > due to a bug in Hurd's implementation of /proc/self/exe (and /proc//exe): > The path returned should always be absolute, not relative. That g

Re: hurd: update RPC prototypes

2017-09-07 Thread Pedro Alves
On 09/06/2017 11:11 PM, Samuel Thibault wrote: > Pedro Alves, on lun. 04 sept. 2017 13:14:33 +0100, wrote: >> On 08/27/2017 07:41 PM, Samuel Thibault wrote: >>> Since hurd's baf7e5c ('hurd: Use polymorphic port types to return some >>> rights.'), some RPCs prototypes have changed, gdb needs the >>

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

2017-09-07 Thread Svante Signell
Hi, When working on porting gccgo to gcc-7, I found out that many test failures are due to a bug in Hurd's implementation of /proc/self/exe (and /proc//exe): The path returned should always be absolute, not relative. Adding print statements to libbacktrace/posix.c shows the problem: GNU/Linux: .