-
Notifications
You must be signed in to change notification settings - Fork 18k
runtime: TestGdbPythonCgo fails on x1 Linux #27608
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
I am currently working on patching this. Seems like the new gdb add address on map key and value, and the "info local" has different output. |
Change https://golang.org/cl/135055 mentions this issue: |
Hello. I Have the same error in an Ubuntu-like :
|
@darcosion This issue is closed and is believed to be fixed. You didn't mention which version you are running: is it before or after the fix, which went into the tree for the future 1.12 on October 1? |
Oh, I'm in the 1.11. I think it's the problem. Thanks for this response. |
I think the fix is still fragile. The patched version still isn't fixed my gdb's output. What I see my gdb 8.2-3 producing for "info locals" is:
which does not match the pair of infoLocalsRe test expressions:
It seems as though the gdb 8.2 @shuLhan tested against produced slicevar and then mapvar, whereas with my instance it's producing mapvar then slicevar. My version of gdb is from fedora 29
Layering even more re complexity into this seems like a bad idea, but here's an re that tries to accommodate mapvar appearing either before or after the slicevar, or not appearing at all:
|
@jimrobinson If you recompiling Go from source (using master branch, not Go 1.1x source), make sure you fetch the latest commits. The test conditional checks in [1] https://github.com/golang/go/blob/master/src/runtime/runtime-gdb_test.go#L269 |
Thank you, that looks like a better solution than adding more complicated re. |
Change https://golang.org/cl/160799 mentions this issue: |
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes, I'm at tip.
What operating system and processor architecture are you using (
go env
)?What did you do?
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
Try to install the latest version of Go from source, running
all.bash
.What did you expect to see?
PASS.
What did you see instead?
The text was updated successfully, but these errors were encountered: