Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

syscall: SIGSYS: bad system call on OpenBSD-current (1/14/2013-snapshot) #4683

Closed
gopherbot opened this issue Jan 22, 2013 · 3 comments
Closed

syscall: SIGSYS: bad system call on OpenBSD-current (1/14/2013-snapshot) #4683

gopherbot opened this issue Jan 22, 2013 · 3 comments
Milestone

Comments

@gopherbot
Copy link

@gopherbot gopherbot commented Jan 22, 2013

by yourcomputerpal:

Before filing a bug, please check whether it has been fixed since the
latest release. Search the issue tracker and check that you're running the
latest version of Go:

Run "go version" and compare against
http://golang.org/doc/devel/release.html  If a newer version of Go exists,
install it and retry what you did to reproduce the problem.

Thanks.

What steps will reproduce the problem?
If possible, include a link to a program on play.golang.org.
1. Running openbsd snapshot from 1/14/2013, amd64
2. Pulled tip and tried to build with ./make.bash
changeset:   15428:073d912321cc


What is the expected output?
Build the toolchain.

What do you see instead?
pkg/go/build
cmd/go
SIGSYS: bad system call
PC=0x4463c6

syscall.Syscall()
        /home/bmercer/go/src/pkg/syscall/asm_openbsd_amd64.s:15 +0x5
syscall.Stat(0xf840062a20, 0xf80000001a, 0xf840078090, 0x0, 0x0, ...)
        /home/bmercer/go/src/pkg/syscall/zsyscall_openbsd_amd64.go:1120 +0x94
os.Stat(0xf840062a20, 0xf80000001a, 0x0, 0x0, 0x0, ...)
        /home/bmercer/go/src/pkg/os/file_unix.go:132 +0x6f
os/exec.findExecutable(0xf840062a20, 0x7f7f0000001a, 0x14, 0x5b45d4, 0x2f000000$
1, ...)
        /home/bmercer/go/src/pkg/os/exec/lp_unix.go:19 +0x2f
os/exec.LookPath(0x5be764, 0x6763636700000005, 0xf840056060, 0xf84006f550, 0x0, 
...)
        /home/bmercer/go/src/pkg/os/exec/lp_unix.go:51 +0x278
main.init()
        /home/bmercer/go/src/cmd/go/bootstrap.go:1319 +0x501

goroutine 2 [runnable]:
created by runtime.main
        /home/bmercer/go/src/pkg/runtime/proc.c:221

Which compiler are you using (5g, 6g, 8g, gccgo)?


Which operating system are you using?
OpenBSD amd64

Which version are you using?  (run 'go version')
NA

Please provide any additional information below.
@4a6f656c
Copy link
Contributor

@4a6f656c 4a6f656c commented Jan 22, 2013

Comment 2:

This is rather bizarre - none of the OpenBSD syscalls have changed since September 2012
and the sys_stat syscall has remained unchanged since 2004. I have not been able to
reproduce the issue here. The reporter is attempting to gather some additional
information.

Owner changed to @4a6f656c.

Status changed to WaitingForReply.

@gopherbot
Copy link
Author

@gopherbot gopherbot commented Jan 22, 2013

Comment 3 by yourcomputerpal:

I built a -current kernel, deleted my go src tree, did a fresh pull and things are
working. I did find out what was causing the issue and it looks like maybe I pulled
-release instead of -tip. 
6167 go_bootstrap CALL  #251 (obsolete rfork)()
6167 go_bootstrap PSIG  SIGSYS caught handler=0x44655b mask=0<>
6167 go_bootstrap RET   #251 (obsolete rfork) -1 errno 78 Function not implemented
Even though I tried doing an hg up tip, and verified I was on tip, there must have been
some stale binary laying around that had that in it? This can be closed. Thanks
@minux
Copy link
Member

@minux minux commented Jan 22, 2013

Comment 4:

Status changed to Retracted.

@rsc rsc added this to the Go1.1 milestone Apr 14, 2015
@rsc rsc removed the go1.1 label Apr 14, 2015
@golang golang locked and limited conversation to collaborators Jun 24, 2016
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.