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

2017-09-21 Thread Svante Signell
On Thu, 2017-09-21 at 01:01 +0200, Samuel Thibault wrote: > Svante Signell, on mer. 20 sept. 2017 08:46:49 +0200, wrote: > > I changed the patch for __execve() to keep file_name if the path is absolute > > and > > call realpath() for relative paths. > > But then if you call a script that looks at

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

2017-09-21 Thread Svante Signell
On Thu, 2017-09-21 at 09:39 +0200, Svante Signell wrote: > On Thu, 2017-09-21 at 01:01 +0200, Samuel Thibault wrote: > > Svante Signell, on mer. 20 sept. 2017 08:46:49 +0200, wrote: > > > I changed the patch for __execve() to keep file_name if the path is > > > absolute > > > and > > > call realpat

Re: [PATCH] eth-multiplxer: Implement ds_device_close()

2017-09-21 Thread Justus Winter
Hi :) "Joan Lledó" writes: > Hello, > > One difference between pfinet and lwip translators is that pfinet doesn't > delete interfaces (or I haven't found how to do it) while lwip does. For > instance, if one starts pfinet with: > > settrans -fga /servers/socket/2 /hurd/pfinet -i /dev/eth1 -a 1

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

2017-09-21 Thread Samuel Thibault
Svante Signell, on jeu. 21 sept. 2017 10:11:42 +0200, wrote: > Sorry. Now I've built glibc successfully. > Should this warning be fixed with a cast too? Casting is almost never the right solution. And here it's for a good reason: file_name is not to be modified, or more importantly, freed. You n