-
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
Make GDB Python Pretty Printers loadable after spawning GDB, avoiding required rust-gdb
#111962
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @Mark-Simulacrum (or someone else) soon. Please see the contribution instructions for more information. Namely, in order to ensure the minimum review times lag, PR authors and assigned reviewers should ensure that the review label (
|
Just a nitpick: this could use a better title, something that describes what it does (see other PR titles for example). Then the "Fixes ###" part can be put in the PR description body, which will link to it and close the issue when this PR merges. |
rust-gdb
Thanks! Fixed that. |
I understand it outmodes rust-gdb, but it does not break it, correct? "defunct" is a word that can be interpreted both ways. |
You are correct. Terribly poor phrasing by me. Will be changed. |
It might be a phrasing that can invite confusion, but I wouldn't call it "terribly poor" at all! Many of the ways you could put it have that dual meaning, tilting towards one, with more or less squinting required to interpret it as the other meaning based on context. |
@pnkfelix this would let Pernosco load these features in the embedded gdb too |
r=me with commits squashed |
Makes the Python pretty printer library source'able from within GDB after spawn. This makes `rust-gdb` not the required approach. It also provides the possibility for GUI:s that wrap GDB, to debug Rust using the pretty printer library; as well as other projects such as for instance Pernosco, which previously was not possible. This won't introduce any new unexpected behaviors for users of `rust-gdb`
I'm not sure I did that right? |
@bors r+ rollup The approval doesn't go in the commit, it needs to be done by one of the reviewer team members. But this is fine. |
…ulacrum Make GDB Python Pretty Printers loadable after spawning GDB, avoiding required `rust-gdb` Fixes rust-lang#111961 Makes the Python pretty printer library source'able from within GDB after spawn, making the wrapper script `rust-gdb` become not the required approach to use the pretty printer library. Allows for integration into GUI:s that wrap GDB extremely easy. The previous design complicates this feature.
…iaskrgr Rollup of 7 pull requests Successful merges: - rust-lang#111058 (Correct fortanix LVI test print function) - rust-lang#111369 (Added custom risc32-imac for esp-espidf target) - rust-lang#111962 (Make GDB Python Pretty Printers loadable after spawning GDB, avoiding required `rust-gdb`) - rust-lang#112019 (Don't suggest changing `&self` and `&mut self` in function signature to be mutable when taking `&mut self` in closure) - rust-lang#112199 (Fix suggestion for matching struct with `..` on both ends) - rust-lang#112220 (Cleanup some `EarlyBinder::skip_binder()` -> `EarlyBinder::subst_identity()`) - rust-lang#112325 (diagnostics: do not suggest type name tweaks on type-inferred closure args) r? `@ghost` `@rustbot` modify labels: rollup
Fixes #111961
Makes the Python pretty printer library source'able from within GDB after spawn, making the wrapper script
rust-gdb
become not the required approach to use the pretty printer library.Allows for integration into GUI:s that wrap GDB extremely easy. The previous design complicates this feature.