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

2017-09-14 Thread Svante Signell
On Mon, 2017-09-11 at 10:52 +0200, Svante Signell wrote: > On Sat, 2017-09-09 at 22:04 +0200, Samuel Thibault wrote: > > Svante Signell, on sam. 09 sept. 2017 10:51:36 +0200, wrote: > > > > > Which programs do you run? > > > > execv/spawn are called from the parent, so the program that needs > >

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

2017-09-14 Thread Samuel Thibault
Svante Signell, on jeu. 14 sept. 2017 14:10:05 +0200, wrote: > With the updated patch things works fine: Cool :) > + __execve (const char *file_name, char *const argv[], char *const envp[]) > + { > + error_t err; > +- file_t file = __file_name_lookup (file_name, O_EXEC, 0); > + > +- if (file

Re: SIGILL instead of SIGSEGV: Was: Re: BUG: /proc/self/exe reports relative paths, should always return absolute paths?

2017-09-14 Thread Samuel Thibault
Svante Signell, on lun. 11 sept. 2017 12:19:35 +0200, wrote: > > This is another bug in the backtrace. hex2dec('deadbeef')/1024^3 = 3.4794 > > GiB > > Even if the address is outside the gnumach range, the program should not > > fail > > with a SIGILL. Or? > > Any ideas why the signal is SIGILL i