You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I compiled this program, call it bogo.go, with go build bogo.go.
Then I run go tool objdump -S ./bogo > bogo.s
package main
func main() {
println("Try 'go tool objdump -S ./bogo > bogo.s'")
loop()
}
var x int64
func loop() {
//line bogo.go:9999999
for x <= 1024*1024*1024 {
x = x + 1
}
}
dmitshur
added
NeedsFix
The path to resolution is known, but the work has not been done.
and removed
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
labels
Jun 8, 2020
What version of Go are you using (
go version
)?Go almost-14
Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
I compiled this program, call it
bogo.go
, withgo build bogo.go
.Then I run
go tool objdump -S ./bogo > bogo.s
What did you expect to see?
Not a panic
What did you see instead?
This is related to #36570 (which is fixed).
Using similar methods I tried to crash both test coverage and pprof, but was unable to provoke a panic.
The text was updated successfully, but these errors were encountered: