-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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
x/debug: viewcore tool don't support dumps with go1.13.3+ #38638
Comments
CC @randall77 |
Change https://golang.org/cl/232158 mentions this issue: |
Change https://golang.org/cl/232160 mentions this issue: |
Change https://golang.org/cl/232161 mentions this issue: |
Arenas used to be allocated completely (or at least, have a span allocated to represent the unused space). Since 1.13.3, the latest arena only has spans up to its highest allocation point. Fixes viewcore for 1.13.3. This change was CL 189957, backported to 1.13 at CL 198485. Update golang/go#38638 Change-Id: Ia8cb14925cf6f4226a80e7ff4f011aa93e8b41d1
Arenas used to be allocated completely (or at least, have a span allocated to represent the unused space). Since 1.13.3, the latest arena only has spans up to its highest allocation point. Fixes viewcore for 1.13.3. This change was CL 189957, backported to 1.13 at CL 198485. Update golang/go#38638 Change-Id: Ia8cb14925cf6f4226a80e7ff4f011aa93e8b41d1
mspan.state used to (go1.13) be a uint8, now (go1.14) it is a struct with a uint8 field. Update golang/go#38638 Change-Id: I042787a61479808d37afa0a7f8caed06b5a18567
Free spans are now implicit. Derive the free span information by finding all the memory in the inuse address ranges that isn't attributed to any span. Fixes viewcore for all versions of 1.14. Also works for tip. Fixes golang/go#38638 Change-Id: Ied283f59391aad8ed5b1b657d2fd6e89e9e9ae6c
With commits in bozaro's repo, test.go works. But my go program(with cgo) still panic: go version go1.14.1 linux/amd64
|
Arenas used to be allocated completely (or at least, have a span allocated to represent the unused space). Since 1.13.3, the latest arena only has spans up to its highest allocation point. Fixes viewcore for 1.13.3. This change was CL 189957, backported to 1.13 at CL 198485. Update golang/go#38638 Change-Id: Ia8cb14925cf6f4226a80e7ff4f011aa93e8b41d1 Reviewed-on: https://go-review.googlesource.com/c/debug/+/232158 Run-TryBot: Keith Randall <khr@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Hyang-Ah Hana Kim <hyangah@gmail.com>
mspan.state used to (go1.13) be a uint8, now (go1.14) it is a struct with a uint8 field. Update golang/go#38638 Change-Id: I042787a61479808d37afa0a7f8caed06b5a18567 Reviewed-on: https://go-review.googlesource.com/c/debug/+/232160 Run-TryBot: Keith Randall <khr@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Hyang-Ah Hana Kim <hyangah@gmail.com> Reviewed-by: Michael Knyszek <mknyszek@google.com>
@randall77 Is there anything else to do here? |
Yes, just waiting on a +2. I'll ping the CL. |
What version of Go are you using (
go version
)?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?
Make some dumps with steps from https://github.com/golang/debug/blob/master/internal/gocore/testdata/README
With go 1.13.2 it's works as expected:
But with go 1.13.3 I got panic:
With go 1.14.2 I got another panic:
I try update
golang.org/x/sys
vendor tov0.0.0-20200420163511-1957bb5e6d1f
but behavior has not changed.The text was updated successfully, but these errors were encountered: