rust/src/test/debuginfo/method-on-tuple-struct.rs, branch try-perfhttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=try-perf2023-01-11T09:32:08+00:00Move /src/test to /tests2023-01-11T09:32:08+00:00Albert Larsan74931857+albertlarsan68@users.noreply.github.com2023-01-05T08:13:28+00:00urn:sha1:cf2dff2b1e3fa55fa5415d524200070d0d7aacfeRemove box syntax from most places in src/test outside of the issues dir2021-09-26T02:07:44+00:00est31MTest31@outlook.com2021-08-25T00:39:40+00:00urn:sha1:6550021124451628b1efc60c59284465b109e3aaImplement new gdb/lldb pretty-printers2020-06-09T13:13:11+00:00ortemortem00@gmail.com2019-05-14T12:50:58+00:00urn:sha1:47c26e69a986d25ed9d26aebc2787334956a89ae
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 licenses2018-12-26T04:08:33+00:00Mark Rousskovmark.simulacrum@gmail.com2018-12-25T15:56:47+00:00urn:sha1:2a663555ddf36f6b041445894a8c175cd1bc718cUpdate enum debuginfo tests2018-10-30T18:09:04+00:00Tom Tromeytom@tromey.com2018-09-26T18:58:10+00:00urn:sha1:8bbb62f849c6b97900751ac0f0cff0d4c9b1328a
Bug #52452 notes some debuginfo test regressions when moving to gdb
8.1. This series will also cause versions of gdb before 8.2 to fail
when a recent LLVM is used -- DW_TAG_variant_part support was not
added until 8.2.
This patch updates one of the builders to a later version of Ubuntu,
which comes with gdb 8.2. It updates the relevant tests to require
both a new-enough LLVM and a new-enough gdb; the subsequent patch
arranges to continue testing the fallback mode.
The "gdbg" results are removed from these tests because the tests now
require a rust-enabled gdb.
If you read closely, you'll see that some of the lldb results in this
patch still look a bit strange. This will be addressed in a
subsequent patch; I believe the fix is to disable the Python
pretty-printers when lldb is rust-enabled.
Run debuginfo tests against rust-enabled lldb, when possible2018-10-08T17:04:24+00:00Tom Tromeytom@tromey.com2018-10-02T16:13:30+00:00urn:sha1:ac33b2e578de58016271012452e4f1be6af9d516
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.
adapt debuginfo tests for gdb with native rust support2016-10-31T20:12:59+00:00Tim Neumannmail@timnn.me2016-10-25T21:32:04+00:00urn:sha1:9253e1206e91f5bd7fafd18f8488a937b0046959Feature-gate `#[no_debug]` and `#[omit_gdb_pretty_printer_section]`2015-09-19T23:39:25+00:00Andrew Paseltinerapaseltiner@gmail.com2015-09-19T20:33:47+00:00urn:sha1:6fa0ff25bdc5aa5aae00dbe7c1cafc927b6806b6
Closes #28091.
Add a name for tuple fields in debuginfo so that they can be accessed in debuggers.2015-04-12T18:44:25+00:00Michael Woeristermichaelwoerister@posteo2015-04-06T18:39:51+00:00urn:sha1:03f92694966259ee156bb8f3a7ef9d4dc587ecb9Fallout in tests2015-04-01T15:22:39+00:00Niko Matsakisniko@alum.mit.edu2015-03-30T13:38:27+00:00urn:sha1:890ed5c46847fa544278c18fd46c1bdfe2809c09