-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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
runtime: Crash in golang 1.4.2 on HardenedBSD 11-CURRENT/amd64 w/o COMPAT_FREEBSD32 #12123
Comments
@lattera can you please check if this is a regression from Go 1.4.2. |
Sure. Which prior version of golang would you like me to test? |
@lattera i'm really sorry, I thought this report was Go 1.5rc1 did not pass on your system. You can try 1.5rc1 if you like, but I suspect it won't pass either. |
Gotcha. I tried with 1.4 and that didn't seem to work, either. |
Nor did 1.3.2. |
FWIW, vanilla FreeBSD 11-CURRENT/amd64 works fine. I wonder if it's because of our ASLR implementation. |
Almost certainly. To this best of my knowledge nobody has reported running On Thu, 13 Aug 2015 08:11 Shawn Webb notifications@github.com wrote:
|
This provides some interesting insight: https://code.google.com/p/go/issues/detail?id=7056 |
Rebuilding kernel with COMPAT_FREEBSD32 and retesting. Will have results soon. |
I believe that issue is fixed on 1.5, Please try the 1.5rc1 release and see if it improves the situation. Thanks Dave On Thu, 13 Aug 2015 08:14 Shawn Webb notifications@github.com wrote:
|
Confirmed. Adding COMPAT_FREEBSD32 to my kernel config solves this issue. Sorry for the duplicate bug and the line noise. I'm glad to see 1.5 will switch golang over to SYSCALL. |
Go is broken on HardenedBSD currently. It appears to be from the hand-written assembly code in
src/runtime/sys_freebsd_amd64.s
. The bug can be triggered simply by attempting to compile go on HardenedBSD 11-CURRENT/amd64.uname -a:
gdb backtrace:
The text was updated successfully, but these errors were encountered: