nordic-dev.net/rust
nordic-dev.net/rust
2
0
Fork 0
mirror of https://github.com/rust-lang/rust.git synced 2024-11-27 09:14:20 +00:00
Code Issues Packages Projects Releases Wiki Activity
0655ed234f
rust/tests/debuginfo/cross-crate-spans.rs

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

77 lines
2.0 KiB
Rust
Raw Normal View History

Feature-gate `#[no_debug]` and `#[omit_gdb_pretty_printer_section]` Closes #28091.
2015-09-19 20:33:47 +00:00
#![feature(omit_gdb_pretty_printer_section)]
Encode codemap and span information in crate metadata. 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.
2015-02-11 17:29:49 +00:00
#![omit_gdb_pretty_printer_section]
//@ min-lldb-version: 310
Update enum debuginfo tests 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-09-26 18:58:10 +00:00
// This fails on lldb 6.0.1 on x86-64 Fedora 28; so mark it macOS-only
// for now.
//@ only-macos
Encode codemap and span information in crate metadata. 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.
2015-02-11 17:29:49 +00:00
//@ aux-build:cross_crate_spans.rs
extern crate cross_crate_spans;
//@ compile-flags:-g
// === GDB TESTS ===================================================================================
Remove licenses
2018-12-25 15:56:47 +00:00
// gdb-command:break cross_crate_spans.rs:14
Encode codemap and span information in crate metadata. 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.
2015-02-11 17:29:49 +00:00
// gdb-command:run
// gdb-command:print result
adapt debuginfo tests for gdb with native rust support
2016-10-25 21:32:04 +00:00
// gdbg-check:$1 = {__0 = 17, __1 = 17}
// gdbr-check:$1 = (17, 17)
Encode codemap and span information in crate metadata. 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.
2015-02-11 17:29:49 +00:00
// gdb-command:print a_variable
// gdb-check:$2 = 123456789
// gdb-command:print another_variable
// gdb-check:$3 = 123456789.5
// gdb-command:continue
// gdb-command:print result
adapt debuginfo tests for gdb with native rust support
2016-10-25 21:32:04 +00:00
// gdbg-check:$4 = {__0 = 1212, __1 = 1212}
// gdbr-check:$4 = (1212, 1212)
Encode codemap and span information in crate metadata. 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.
2015-02-11 17:29:49 +00:00
// gdb-command:print a_variable
// gdb-check:$5 = 123456789
// gdb-command:print another_variable
// gdb-check:$6 = 123456789.5
// gdb-command:continue
// === LLDB TESTS ==================================================================================
Remove licenses
2018-12-25 15:56:47 +00:00
// lldb-command:b cross_crate_spans.rs:14
Encode codemap and span information in crate metadata. 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.
2015-02-11 17:29:49 +00:00
// lldb-command:run
Use explicit LLDB commands instead of `print`/`p` aliases.
2024-03-15 14:05:57 +00:00
// lldb-command:v result
Remove LLDB persistent results in `compiletest`.
2024-03-10 13:55:58 +00:00
// lldbg-check:[...] { 0 = 17 1 = 17 }
Implement new gdb/lldb pretty-printers 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.
2019-05-14 12:50:58 +00:00
// lldbr-check:((u32, u32)) result = { 0 = 17 1 = 17 }
Use explicit LLDB commands instead of `print`/`p` aliases.
2024-03-15 14:05:57 +00:00
// lldb-command:v a_variable
Remove LLDB persistent results in `compiletest`.
2024-03-10 13:55:58 +00:00
// lldbg-check:[...] 123456789
Run debuginfo tests against rust-enabled lldb, when possible 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.
2018-10-02 16:13:30 +00:00
// lldbr-check:(u32) a_variable = 123456789
Use explicit LLDB commands instead of `print`/`p` aliases.
2024-03-15 14:05:57 +00:00
// lldb-command:v another_variable
Remove LLDB persistent results in `compiletest`.
2024-03-10 13:55:58 +00:00
// lldbg-check:[...] 123456789.5
Run debuginfo tests against rust-enabled lldb, when possible 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.
2018-10-02 16:13:30 +00:00
// lldbr-check:(f64) another_variable = 123456789.5
Encode codemap and span information in crate metadata. 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.
2015-02-11 17:29:49 +00:00
// lldb-command:continue
Use explicit LLDB commands instead of `print`/`p` aliases.
2024-03-15 14:05:57 +00:00
// lldb-command:v result
Remove LLDB persistent results in `compiletest`.
2024-03-10 13:55:58 +00:00
// lldbg-check:[...] { 0 = 1212 1 = 1212 }
Implement new gdb/lldb pretty-printers 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.
2019-05-14 12:50:58 +00:00
// lldbr-check:((i16, i16)) result = { 0 = 1212 1 = 1212 }
Use explicit LLDB commands instead of `print`/`p` aliases.
2024-03-15 14:05:57 +00:00
// lldb-command:v a_variable
Remove LLDB persistent results in `compiletest`.
2024-03-10 13:55:58 +00:00
// lldbg-check:[...] 123456789
Run debuginfo tests against rust-enabled lldb, when possible 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.
2018-10-02 16:13:30 +00:00
// lldbr-check:(u32) a_variable = 123456789
Use explicit LLDB commands instead of `print`/`p` aliases.
2024-03-15 14:05:57 +00:00
// lldb-command:v another_variable
Remove LLDB persistent results in `compiletest`.
2024-03-10 13:55:58 +00:00
// lldbg-check:[...] 123456789.5
Run debuginfo tests against rust-enabled lldb, when possible 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.
2018-10-02 16:13:30 +00:00
// lldbr-check:(f64) another_variable = 123456789.5
Encode codemap and span information in crate metadata. 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.
2015-02-11 17:29:49 +00:00
// lldb-command:continue
// This test makes sure that we can break in functions inlined from other crates.
fn main() {
let _ = cross_crate_spans::generic_function(17u32);
let _ = cross_crate_spans::generic_function(1212i16);
}
Reference in New Issue Copy Permalink