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
net/http: panic: runtime error: index out of range #15145
Comments
It happened again http://build.golang.org/log/e29df5d52f88ce13b851539511ec5bd4d05b4cb5 |
If you just want to see the autogenerated code: Not 100% sure but maybe this could be the auto generated pointer receiver version of: This shows for me on OSX:
|
@randall77, I'm going to assume this is a code generation issue for now and not actually a net/http problem? |
I don't see anything obviously wrong from the code. This is the autogenerated code for
The call out to It's weird that the error is "index out of range". There are no bounds checks in this stub. The only non-race thing it calls is I don't know what might be windows-specific about this. I'm going to try to reproduce on linux overnight. |
It is quite possible. But then I expect trace to say:
and not
And here I have built windows-amd64-race test exe on my system:
Alex |
I was unable to reproduce this bug overnight on linux/amd64. |
reproduced with GOTRACEBACK=system enabled:
@aclements looks like something to do with stack barriers. |
CL https://golang.org/cl/21931 mentions this issue. |
I wonder if we should set GOTRACEBACK=2 on all
the builders.
|
@minux, probably. File a bug? |
Just seen on windows-amd64-race builder http://build.golang.org/log/81d3f339f9c1248dcbd80defc911b338d61c4118
I am not sure what to do here. But I am also confused about
<autogenerated>:113
in stack trace. I wonder what happened here. Am I missing something?Alex
The text was updated successfully, but these errors were encountered: