tech-kern archive

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

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

To: maya%netbsd.org@localhost
Subject: Re: Go binary panics on amd64-current - SIG*unknown
From: Stephen Ma <stephenm%employees.org@localhost>
Date: Sun, 7 Jan 2018 10:54:19 +1100

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

References:
- Go binary panics on amd64-current - SIG*unknown
  - From: Alexander Nasonov
- Re: Go binary panics on amd64-current - SIG*unknown
  - From: maya

Prev by Date: Re: Go binary panics on amd64-current - SIG*unknown
Next by Date: Re: Go binary panics on amd64-current - SIG*unknown
Previous by Thread: Re: Go binary panics on amd64-current - SIG*unknown
Next by Thread: Re: Go binary panics on amd64-current - SIG*unknown
Indexes:

Home | Main Index | Thread Index | Old Index