-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Test gdb pretty printing more and fix overzealous type substitution #68098
Conversation
(rust_highfive has picked a reviewer for you, use r? to override) |
I think someone recently looked into our gdb pretty printing -- maybe @pnkfelix? Or @michaelwoerister? |
r? @pnkfelix |
FWIW this patch looks reasonable to me. |
cc60b8f
to
44f52ee
Compare
Last push is a (very late) rebase that I had already prepared for #67980 |
(This will need to be rebased atop PR #60826 after that lands.) |
r=me after PR #60826 lands and you do subsequent rebase. |
44f52ee
to
576771a
Compare
Last commit removed the part that isn't in the title and would interfere with #70111. |
Thank you for doing this. FWIW this still looks reasonable to me. |
r=me but would like to wait on #70111 landing I think |
☔ The latest upstream changes (presumably #70205) made this pull request unmergeable. Please resolve the merge conflicts. |
576771a
to
d8a136f
Compare
I noticed that if the key type is (), and you insert an element (the only one ever), pretty printing says the type is undefined. I guess civilization can survive without me logging that as a bug. r? @msimulacrum |
📌 Commit d8a136f has been approved by |
☀️ Test successful - checks-azure |
…r=Mark-Simulacrum Test and fix gdb pretty printing more Over time I had oversimplified the test case for rust-lang#68098: it does not have an internal node to print so it does not test what it pretend to test. And then I also realized not spotting the same mistake reviewing rust-lang#70111, and more likely to occur in the wild. Now, both test cases fail if you put back the flawed python code. r? @Mark-Simulacrum
…Mark-Simulacrum Test and fix gdb pretty printing more Over time I had oversimplified the test case for rust-lang#68098: it does not have an internal node to print so it did not test what it pretended to test. And then I also realized not spotting the same mistake reviewing rust-lang#70111, and more likely to occur in the wild. Now, both test cases fail if you put back the flawed python code. r? @Mark-Simulacrum
Adresses a problem concerning printing BTreeMap / BTreeSet data in gdb: when the key or value type name contains substring "LeafNode", and the map has multiple nodes (e.g. more than 11 elements), printing causes an exception. E.g.
The code was written in #56144 by @tromey (and later touched upon by @RalfJung in #57045, but I think that had nothing to do with the issues in this PR).