Re: Go binary panics on amd64-current - SIG*unknown

On Jan 7, 9:03pm, al...@yandex.ru (Alexander Nasonov) wrote: -- Subject: Re: Go binary panics on amd64-current - SIG*unknown Thanks! Committed (3 x) christos

Re: Go binary panics on amd64-current - SIG*unknown

Christos Zoulas wrote: > Index: linux_sigaction.c > === > RCS file: /cvsroot/src/sys/compat/linux/common/linux_sigaction.c,v > retrieving revision 1.34 > diff -u -u -r1.34 linux_sigaction.c > --- linux_sigaction.c 17 Oct 2008 20:21:34

Re: Go binary panics on amd64-current - SIG*unknown

Ah, I thought I mentioned it in my email. Yes, it’s Linux binary.Sent from Yandex.Mail for mobile: http://m.ya.ru/ymail

Re: Go binary panics on amd64-current - SIG*unknown

In article <20180106224309.w2vicky2i6rf6fvu@neva>, Alexander Nasonov wrote: >I downloaded IACA tool from intel.com but I couldn't run it: > >$ ktrace ./iaca-v3.0-lin64/iaca >fatal error: rt_sigaction read failure > >runtime stack: >runtime.throw(0x75de24, 0x19) >

Re: Go binary panics on amd64-current - SIG*unknown

I think the issue is caused by linux defining signals from 1 to LINUX__NSIG, while the linux compat code in netbsd recognises signals from 1 to LINUX__NSIG-1. That's why the binary is aborting when calling sigaction on signal 64, which is LINUX__NSIG on amd64. - S

Re: Go binary panics on amd64-current - SIG*unknown

On Sat, Jan 06, 2018 at 10:43:09PM +, Alexander Nasonov wrote: > runtime.getsig(0x40, 0x441c60) > /nfs/iil/disks/kfw/tools/go/go-latest/src/runtime/os_linux.go:427 > +0x92 Is that a linux binary? that seems to come from:

Go binary panics on amd64-current - SIG*unknown

I downloaded IACA tool from intel.com but I couldn't run it: $ ktrace ./iaca-v3.0-lin64/iaca fatal error: rt_sigaction read failure runtime stack: runtime.throw(0x75de24, 0x19) /nfs/iil/disks/kfw/tools/go/go-latest/src/runtime/panic.go:596 +0x95 runtime.getsig(0x40, 0x441c60)