-
Notifications
You must be signed in to change notification settings - Fork 18k
net/http/pprof, cmd/internal/objfile: panic: runtime error: slice bounds out of range in disasm.go #36621
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
Looks related to #36570, but likely more serious since it affects pprof rather than objdump. |
@javasgl You did not fill out the bug template, you just deleted it. Please fill out the template. We need that information. Thanks. |
Is the code being disassembled is an infinite loop? |
Change https://golang.org/cl/215297 mentions this issue: |
I tried to reproduce this several ways, and failed. We need more information.
I tried web, weblist, and disasm within |
I think he's working with 1.12 or earlier, because the panic message has no array bounds contents, and that change went in for 1.13. The bogus line number was also introduced in 1.13, so this may be related, but is a different error than #36570 . Could the original poster try this with 1.13, 1.14beta1, or tip? It is entirely possible it is fixed. Also what @ianlancetaylor said - please fill out the template so we don't have to guess as to what Go version / OS / etc. you're using. |
Might not be closed, was a gaffe in the commit wording. |
Kindly pinging you @javasgl, it’s been about 3 weeks since Ian requested that you fill out the issue template to indicate the preliminary information like Go version. Keith matched it up to Go1.12 and earlier from debugging. We are about to roll out Go1.14 so please respond ASAP, but we can also move this to the backlog milestone. |
go version: 1.12.9 |
Cool, thank you @javasgl, if you can consistently reproduce this bug, please try with Go1.14rc1 as per https://golang.org/dl/#unstable with go get golang.org/dl/go1.14rc1 and then go1.14rc1 run main.go and then let us know the results, most likely the bug won't come back. Thank you again. |
I tried go1.13.6 , go1.13.7 and go1.14rc1, i can't reproduce this bug may be 1.13.x has fixed this bug |
Gotcha, great to hear that it no longer reproduces! Alright, so I'll close this bug, but please don't hesitate to file other bugs or seek out. I look forward to seeing more of you in the Go community and thank you for using Go and for reporting this issue! |
go/src/cmd/internal/objfile/disasm.go
Line 271 in 574c286
panic in here
The text was updated successfully, but these errors were encountered: