about summary refs log tree commit diff
path: root/src/test/debuginfo/cross-crate-spans.rs
AgeCommit message (Collapse)AuthorLines
2018-12-25Remove licensesMark Rousskov-12/+2
2018-10-30Update enum debuginfo testsTom Tromey-0/+4
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.
2018-10-08Run debuginfo tests against rust-enabled lldb, when possibleTom Tromey-6/+12
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.
2016-10-31adapt debuginfo tests for gdb with native rust supportTim Neumann-2/+4
2015-09-19Feature-gate `#[no_debug]` and `#[omit_gdb_pretty_printer_section]`Andrew Paseltiner-2/+3
Closes #28091.
2015-04-29Re-enable tests on AndroidTamir Duberstein-1/+0
Addresses part of #10381.
2015-04-28#10381: WarningsTamir Duberstein-2/+2
2015-04-12Add a name for tuple fields in debuginfo so that they can be accessed in ↵Michael Woerister-2/+2
debuggers.
2015-03-04Encode codemap and span information in crate metadata.Michael Woerister-0/+74
This allows to create proper debuginfo line information for items inlined from other crates (e.g. instantiations of generics). Only the codemap's 'metadata' is stored in a crate's metadata. That is, just filename, line-beginnings, etc. but not the actual source code itself. We are thus missing the opportunity of making Rust the first "open-source-only" programming language out there. Pity.