[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: SIGILL instead of SIGSEGV: Was: Re: BUG: /proc/self/exe reports rela

From: Samuel Thibault
Subject: Re: SIGILL instead of SIGSEGV: Was: Re: BUG: /proc/self/exe reports relative paths, should always return absolute paths?
Date: Fri, 15 Sep 2017 01:53:45 +0200
User-agent: NeoMutt/20170113 (1.7.2)

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 instead of SIGSEGV? How to trace the cause 
> of
> this bug?

I don't think it's a "bug" per se. The address you give is outside
the valid userland range, so the x86 trap is different, so it's not
surprising that the signal is different. You could put printfs in
gnumach's user_trap() function to see what triggers it precisely.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]