rust/src/test/debuginfo/simple-tuple.rs, branch 1.56.0

Update cdb tests for expected output

2021-07-01T18:26:20+00:00

Also an fix issue with tuple type names where we can't cast to them in natvis (required by the visualizer for `HashMap`) because of peculiarities with the natvis expression evaluator.

Improve debug symbol names to avoid ambiguity and work better with MSVC's debugger

2021-06-30T18:10:29+00:00

There are several cases where names of types and functions in the debug info are either ambiguous, or not helpful, such as including ambiguous placeholders (e.g., `{{impl}}`, `{{closure}}` or `dyn _'`) or dropping qualifications (e.g., for dynamic types). Instead, each debug symbol name should be unique and useful: * Include disambiguators for anonymous `DefPathDataName` (closures and generators), and unify their formatting when used as a path-qualifier vs item being qualified. * Qualify the principal trait for dynamic types. * If there is no principal trait for a dynamic type, emit all other traits instead. * Respect the `qualified` argument when emitting ref and pointer types. * For implementations, emit the disambiguator. * Print const generics when emitting generic parameters or arguments. Additionally, when targeting MSVC, its debugger treats many command arguments as C++ expressions, even when the argument is defined to be a symbol name. As such names in the debug info need to be more C++-like to be parsed correctly: * Avoid characters with special meaning (`#`, `[`, `"`, `+`). * Never start a name with `<` or `{` as this is treated as an operator. * `>>` is always treated as a right-shift, even when parsing generic arguments (so add a space to avoid this). * Emit function declarations using C/C++ style syntax (e.g., leading return type). * Emit arrays as a synthetic `array$` type. * Include a `$` in all synthetic types as this is a legal character for C++, but not Rust (thus we avoid collisions with user types).

Modify type names on MSVC to make tuples .natvis compatible.

2020-06-25T02:28:12+00:00

- Mangles (T0, T1) as tuple, possibly unblocking rust-lang/rust#70052 "Update hashbrown to 0.8.0" - Prettifies Rust tuples similar to VS2017's std::tuple - Improves debuginfo test coverage

Implement new gdb/lldb pretty-printers

2020-06-09T13:13:11+00:00

Replace old GDB and LLDB pretty-printers with new ones which were originally written for IntelliJ Rust. New LLDB pretty-printers support synthetic children. New GDB/LLDB pretty-printers support all Rust types supported by old pretty-printers, and also support: Rc, Arc, Cell, Ref, RefCell, RefMut, HashMap, HashSet.

Remove licenses

2018-12-26T04:08:33+00:00

Run debuginfo tests against rust-enabled lldb, when possible

2018-10-08T17:04:24+00:00

If the rust-enabled lldb was built, then use it when running the debuginfo tests. Updating the lldb submodule was necessary as this needed a way to differentiate the rust-enabled lldb, so I added a line to the --version output. This adds compiletest commands to differentiate between the rust-enabled and non-rust-enabled lldb, as is already done for gdb. A new "rust-lldb" header directive is also added, but not used in this patch; I plan to use it in #54004. This updates all the tests.

Disable failing tests temporarily

2018-01-05T10:47:34+00:00

update gdbr tests

2017-03-09T21:12:36+00:00

gdb will now reliably detect the lanugage as rust even before any code is run.

adapt debuginfo tests for gdb with native rust support

2016-10-31T20:12:59+00:00

Feature-gate `#[no_debug]` and `#[omit_gdb_pretty_printer_section]`

2015-09-19T23:39:25+00:00

Closes #28091.