Date: Thu, 31 Mar 2016 14:16:08 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 208421] lang/go gets stuck when running in a FreeBSD jail Message-ID: <bug-208421-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208421 Bug ID: 208421 Summary: lang/go gets stuck when running in a FreeBSD jail Product: Ports & Packages Version: Latest Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: jlaffaye@FreeBSD.org Reporter: khaelin@gmail.com Assignee: jlaffaye@FreeBSD.org Flags: maintainer-feedback?(jlaffaye@FreeBSD.org) Created attachment 168820 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D168820&action= =3Dedit Full ktrace for go --help ## Go version 1.6 (official freebsd pkg 1.6,1) ## System FreeBSD 10.2 (10.2-RELEASE-p13). Commands executed in a jail. ## Problem Running any kind of go command (even something as simple as `go --help`) in= a jail gets stuck and has to be killed with SIGKILL. There is no such problem when running `go` outside of a jail. ## Trace Running `ktrace go --help`: 72810 go CALL sigaction(SIG 32,0x7fffffffea18,0) 72810 go RET sigaction 0 72810 go CALL clock_gettime(0x4,0xc820020750) 72810 go RET clock_gettime 0 72810 go CALL sigprocmask(SIG_SETMASK,0x7fffffffe970,0x7fffffffe9a0) 72810 go RET sigprocmask 0 72810 go CALL _umtx_op(0x8010ad330,0x11,0,0,0) Full trace attached. I have the exact same problem when executing in a jail a binary built with = `go build` outside a jail. This is the first time we are trying to run our Go software on FreeBSD, so I have no idea whether it is a FreeBSD problem or a Go problem. I also submitted a ticket on the go issue tracker (https://github.com/golang/go/issues/15044) in case this is a go bug. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-208421-13>