The test added for issue #18146 exposed a long-existing bug in the Solaris port; notably, that syscall.Exec uses RawSyscall -- which is not actually functional for the Solaris port (intentionally) and only exists as a placebo to satisfy build requirements.
From syscall_solaris.go:
// This is syscall.RawSyscall, it exists to satisfy some build dependency,// but it doesn't work correctly.//// DO NOT USE!//// TODO(aram): make this panic once we stop calling fcntl(2) in net using it.funcsyscall_rawsyscall(trap, a1, a2, a3uintptr) (r1, r2, erruintptr) {
From syscall/exec_solaris.go:
// We call hand-crafted syscalls, implemented in// ../runtime/syscall_solaris.go, rather than generated libc wrappers// because we need to avoid lazy-loading the functions (might malloc,// split the stack, or acquire mutexes). We can't call RawSyscall// because it's not safe even for BSD-subsystem calls.
Currently, the misc/cgo/test/issue18146.go test fails on Solaris as follows:
$ ./test.test -test.v -test.run Test18146
=== RUN Test18146
--- FAIL: Test18146 (5.99s)
issue18146.go:121: syscall.Exec failed: exit status 1
=== RUN Test18146
--- FAIL: Test18146 (0.00s)
issue18146.go:77: invalid argument
FAIL
issue18146.go:121: syscall.Exec failed: exit status 1
...
The fix is simple and I will submit a change request soon.
The text was updated successfully, but these errors were encountered:
The test added for issue #18146 exposed a long-existing bug in the Solaris port; notably, that syscall.Exec uses RawSyscall -- which is not actually functional for the Solaris port (intentionally) and only exists as a placebo to satisfy build requirements.
From syscall_solaris.go:
From syscall/exec_solaris.go:
Currently, the misc/cgo/test/issue18146.go test fails on Solaris as follows:
The fix is simple and I will submit a change request soon.
The text was updated successfully, but these errors were encountered: