-
Notifications
You must be signed in to change notification settings - Fork 18k
runtime: Figure out how to re-enable TestCgoExternalThreadSignal on dragonfly #11847
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
Comments
CL https://golang.org/cl/12569 mentions this issue. |
Just removed a few images, burned dfly-v4.2.3.2 and run ktrace -id ./runtime.test -test.run=TestCgoExternalThreadSignal. The output of kdump is 2759000 lines, extract around SIGSEGV looks the following:
|
Thanks! This makes it obvious that the problem is that runtime·raise is not implemented correctly for dragonfly. The code in runtime/sys_dragonfly_amd64.s is obviously wrong. What is less clear is what it should look like. Can you give https://golang.org/cl/12621 a try? |
CL https://golang.org/cl/12621 mentions this issue. |
Re-burning... |
It works, congrats.
|
Thanks for testing--want to +2 the CL? |
Oh, you did already--thanks! |
I got this mistake when I build go1.4.3 on my mac
|
@idevz That is a different problem, and this issue is closed. Please open a new bug report. |
@ianlancetaylor thank you every much |
On the Dragonfly builds, TestCgoExternalThreadSignal is failing:
--- FAIL: TestCgoExternalThreadSignal (6.72s)
crash_cgo_test.go:94: expected "OK\n", but got "C signal did not crash as expected\n\n\n"
I'm going to disable the test. We should figure out why it is not working on Dragonfly, and re-enable it.
The text was updated successfully, but these errors were encountered: