-
Notifications
You must be signed in to change notification settings - Fork 18k
runtime: writebarrierptr_nostore1 called with mp.p == nil #10223
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
Any hope of getting the elided frames? From what I'm seeing there is a throw that results in the throw logic also failing and that throw also fails. The cause of the original throw has had its broken stack frame elided. |
That stack is just copy/pasted from a build failure on build.golang.org, which runs all.bash with the default settings. (no custom GOTRACEBACK env vars, etc). But it seems that the |
I just saw that i also failed on a previous commit on the nacl-amd64p32 http://build.golang.org/log/6bc2419376e65f381076f15802ca1fe10e9098d4 It has a better stack trace with no elided frames, but it might be caused by runtime stack: goroutine 33 [runnable, locked to thread]: goroutine 1 [chan receive]: goroutine 15 [runnable]: goroutine 16 [chan receive]: goroutine 17 [semacquire]: goroutine 18 [trace reader (blocked)]: It seems nacl's newosproc should be labeled nowritebarrier? |
Fixing the write barriers in os1_nacl.go's newosproc should fix this On Mon, Mar 23, 2015 at 10:58 PM, Minux Ma notifications@github.com wrote:
|
I've already sent CL 7973 for the nacl issue.
|
windows-amd64 just failed in runtime/pprof tests with:
http://build.golang.org/log/15ccbe982c8df1a9416adcd42f773b2d812f2fc6
/cc @aclements @RLH @rsc @dvyukov
The text was updated successfully, but these errors were encountered: