gdb: Fix pretty-printing special-cased Rust types #35585
Conversation
gdb trunk now reports fully qualified type names, just like lldb. Move lldb code for extracting unqualified names to shared file.
|
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @aturon (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
|
@bors r+ Thanks for the PR, looks good to me! |
|
📌 Commit 4714072 has been approved by |
|
⌛ Testing commit 4714072 with merge 2582133... |
|
💔 Test failed - auto-mac-64-opt |
|
@bors: retry On Tue, Aug 30, 2016 at 12:20 PM, bors notifications@github.com wrote:
|
gdb: Fix pretty-printing special-cased Rust types gdb trunk now reports fully qualified type names, just like lldb. Move lldb code for extracting unqualified names to shared file. For current releases of gdb, `extract_type_name` should just be a no-op. Fixes #35155
gdb trunk now reports fully qualified type names, just like lldb. Move lldb code for extracting unqualified names to shared file.
For current releases of gdb,
extract_type_nameshould just be a no-op.Fixes #35155