mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
00bfd702dc
rust/tests/debuginfo/var-captured-in-nested-closure.rs

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

175 lines
5.6 KiB
Rust
Raw Normal View History

debuginfo: Gate all LLDB debuginfo tests on a minimum LLDB version being available
2014-10-09 09:31:03 -05:00
//@ min-lldb-version: 310
Add make check support(arm-linux-androideabi debuginfo)
2013-11-04 00:53:01 -06:00
Consolidate codegen-related compiler flags Move them all behind a new -C switch. This migrates some -Z flags and some top-level flags behind this -C codegen option. The -C flag takes values of the form "-C name=value" where the "=value" is optional for some flags. Flags affected: * --llvm-args => -C llvm-args * --passes => -C passes * --ar => -C ar * --linker => -C linker * --link-args => -C link-args * --target-cpu => -C target-cpu * --target-feature => -C target-fature * --android-cross-path => -C android-cross-path * --save-temps => -C save-temps * --no-rpath => -C no-rpath * -Z no-prepopulate => -C no-prepopulate-passes * -Z no-vectorize-loops => -C no-vectorize-loops * -Z no-vectorize-slp => -C no-vectorize-slp * -Z soft-float => -C soft-float * -Z gen-crate-map => -C gen-crate-map * -Z prefer-dynamic => -C prefer-dynamic * -Z no-integrated-as => -C no-integrated-as As a bonus, this also promotes the -Z extra-debug-info flag to a first class -g or --debuginfo flag. * -Z debug-info => removed * -Z extra-debug-info => -g or --debuginfo Closes #9770 Closes #12000
2014-02-06 21:57:09 -06:00
//@ compile-flags:-g
debuginfo: Add LLDB autotests to debuginfo test suite. This commit adds LLDB autotests to the test suite but does not activate them by default yet.
2014-07-09 07:46:09 -05:00
// === GDB TESTS ===================================================================================
debuginfo: Split debuginfo autotests into debuginfo-gdb and debuginfo-lldb
2014-04-24 04:35:48 -05:00
// gdb-command:run
debuginfo: Added test cases for structs, tuples, enums, etc passed by value. Also updated documentation comments in debuginfo and renamed DebugContext to CrateDebugContext.
2013-08-29 04:44:11 -05:00
debuginfo: Split debuginfo autotests into debuginfo-gdb and debuginfo-lldb
2014-04-24 04:35:48 -05:00
// gdb-command:print variable
// gdb-check:$1 = 1
// gdb-command:print constant
// gdb-check:$2 = 2
// gdb-command:print a_struct
adapt debuginfo tests for gdb with native rust support
2016-10-25 16:32:04 -05:00
// gdbg-check:$3 = {a = -3, b = 4.5, c = 5}
// gdbr-check:$3 = var_captured_in_nested_closure::Struct {a: -3, b: 4.5, c: 5}
debuginfo: Split debuginfo autotests into debuginfo-gdb and debuginfo-lldb
2014-04-24 04:35:48 -05:00
// gdb-command:print *struct_ref
adapt debuginfo tests for gdb with native rust support
2016-10-25 16:32:04 -05:00
// gdbg-check:$4 = {a = -3, b = 4.5, c = 5}
// gdbr-check:$4 = var_captured_in_nested_closure::Struct {a: -3, b: 4.5, c: 5}
debuginfo: Split debuginfo autotests into debuginfo-gdb and debuginfo-lldb
2014-04-24 04:35:48 -05:00
// gdb-command:print *owned
// gdb-check:$5 = 6
// gdb-command:print closure_local
Test fixes from the rollup
2014-10-02 17:12:58 -05:00
// gdb-check:$6 = 8
debuginfo: Split debuginfo autotests into debuginfo-gdb and debuginfo-lldb
2014-04-24 04:35:48 -05:00
// gdb-command:continue
debuginfo: Added test cases for structs, tuples, enums, etc passed by value. Also updated documentation comments in debuginfo and renamed DebugContext to CrateDebugContext.
2013-08-29 04:44:11 -05:00
debuginfo: Split debuginfo autotests into debuginfo-gdb and debuginfo-lldb
2014-04-24 04:35:48 -05:00
// gdb-command:print variable
Test fixes from the rollup
2014-10-02 17:12:58 -05:00
// gdb-check:$7 = 1
debuginfo: Split debuginfo autotests into debuginfo-gdb and debuginfo-lldb
2014-04-24 04:35:48 -05:00
// gdb-command:print constant
Test fixes from the rollup
2014-10-02 17:12:58 -05:00
// gdb-check:$8 = 2
debuginfo: Split debuginfo autotests into debuginfo-gdb and debuginfo-lldb
2014-04-24 04:35:48 -05:00
// gdb-command:print a_struct
adapt debuginfo tests for gdb with native rust support
2016-10-25 16:32:04 -05:00
// gdbg-check:$9 = {a = -3, b = 4.5, c = 5}
// gdbr-check:$9 = var_captured_in_nested_closure::Struct {a: -3, b: 4.5, c: 5}
debuginfo: Split debuginfo autotests into debuginfo-gdb and debuginfo-lldb
2014-04-24 04:35:48 -05:00
// gdb-command:print *struct_ref
adapt debuginfo tests for gdb with native rust support
2016-10-25 16:32:04 -05:00
// gdbg-check:$10 = {a = -3, b = 4.5, c = 5}
// gdbr-check:$10 = var_captured_in_nested_closure::Struct {a: -3, b: 4.5, c: 5}
debuginfo: Split debuginfo autotests into debuginfo-gdb and debuginfo-lldb
2014-04-24 04:35:48 -05:00
// gdb-command:print *owned
Test fixes from the rollup
2014-10-02 17:12:58 -05:00
// gdb-check:$11 = 6
debuginfo: Split debuginfo autotests into debuginfo-gdb and debuginfo-lldb
2014-04-24 04:35:48 -05:00
// gdb-command:print closure_local
Test fixes from the rollup
2014-10-02 17:12:58 -05:00
// gdb-check:$12 = 8
debuginfo: Split debuginfo autotests into debuginfo-gdb and debuginfo-lldb
2014-04-24 04:35:48 -05:00
// gdb-command:continue
debuginfo: Much improved handling of captured variables and by-value arguments.
2013-09-03 11:23:59 -05:00
debuginfo: Add LLDB autotests to debuginfo test suite. This commit adds LLDB autotests to the test suite but does not activate them by default yet.
2014-07-09 07:46:09 -05:00
// === LLDB TESTS ==================================================================================
// lldb-command:run
Use explicit LLDB commands instead of `print`/`p` aliases.
2024-03-15 09:05:57 -05:00
// lldb-command:v variable
Remove LLDB persistent results in `compiletest`.
2024-03-10 08:55:58 -05:00
// lldbg-check:[...] 1
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 11:13:30 -05:00
// lldbr-check:(isize) variable = 1
Use explicit LLDB commands instead of `print`/`p` aliases.
2024-03-15 09:05:57 -05:00
// lldb-command:v constant
Remove LLDB persistent results in `compiletest`.
2024-03-10 08:55:58 -05:00
// lldbg-check:[...] 2
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 11:13:30 -05:00
// lldbr-check:(isize) constant = 2
Use explicit LLDB commands instead of `print`/`p` aliases.
2024-03-15 09:05:57 -05:00
// lldb-command:v a_struct
Remove LLDB persistent results in `compiletest`.
2024-03-10 08:55:58 -05:00
// lldbg-check:[...] { a = -3 b = 4.5 c = 5 }
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 07:50:58 -05:00
// lldbr-check:(var_captured_in_nested_closure::Struct) a_struct = { a = -3 b = 4.5 c = 5 }
Use explicit LLDB commands instead of `print`/`p` aliases.
2024-03-15 09:05:57 -05:00
// lldb-command:v *struct_ref
Remove LLDB persistent results in `compiletest`.
2024-03-10 08:55:58 -05:00
// lldbg-check:[...] { a = -3 b = 4.5 c = 5 }
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 07:50:58 -05:00
// lldbr-check:(var_captured_in_nested_closure::Struct) *struct_ref = { a = -3 b = 4.5 c = 5 }
Use explicit LLDB commands instead of `print`/`p` aliases.
2024-03-15 09:05:57 -05:00
// lldb-command:v *owned
Remove LLDB persistent results in `compiletest`.
2024-03-10 08:55:58 -05:00
// lldbg-check:[...] 6
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 11:13:30 -05:00
// lldbr-check:(isize) *owned = 6
Use explicit LLDB commands instead of `print`/`p` aliases.
2024-03-15 09:05:57 -05:00
// lldb-command:v closure_local
Remove LLDB persistent results in `compiletest`.
2024-03-10 08:55:58 -05:00
// lldbg-check:[...] 8
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 11:13:30 -05:00
// lldbr-check:(isize) closure_local = 8
debuginfo: Add LLDB autotests to debuginfo test suite. This commit adds LLDB autotests to the test suite but does not activate them by default yet.
2014-07-09 07:46:09 -05:00
// lldb-command:continue
Use explicit LLDB commands instead of `print`/`p` aliases.
2024-03-15 09:05:57 -05:00
// lldb-command:v variable
Remove LLDB persistent results in `compiletest`.
2024-03-10 08:55:58 -05:00
// lldbg-check:[...] 1
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 11:13:30 -05:00
// lldbr-check:(isize) variable = 1
Use explicit LLDB commands instead of `print`/`p` aliases.
2024-03-15 09:05:57 -05:00
// lldb-command:v constant
Remove LLDB persistent results in `compiletest`.
2024-03-10 08:55:58 -05:00
// lldbg-check:[...] 2
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 11:13:30 -05:00
// lldbr-check:(isize) constant = 2
Use explicit LLDB commands instead of `print`/`p` aliases.
2024-03-15 09:05:57 -05:00
// lldb-command:v a_struct
Remove LLDB persistent results in `compiletest`.
2024-03-10 08:55:58 -05:00
// lldbg-check:[...] { a = -3 b = 4.5 c = 5 }
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 07:50:58 -05:00
// lldbr-check:(var_captured_in_nested_closure::Struct) a_struct = { a = -3 b = 4.5 c = 5 }
Use explicit LLDB commands instead of `print`/`p` aliases.
2024-03-15 09:05:57 -05:00
// lldb-command:v *struct_ref
Remove LLDB persistent results in `compiletest`.
2024-03-10 08:55:58 -05:00
// lldbg-check:[...] { a = -3 b = 4.5 c = 5 }
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 07:50:58 -05:00
// lldbr-check:(var_captured_in_nested_closure::Struct) *struct_ref = { a = -3 b = 4.5 c = 5 }
Use explicit LLDB commands instead of `print`/`p` aliases.
2024-03-15 09:05:57 -05:00
// lldb-command:v *owned
Remove LLDB persistent results in `compiletest`.
2024-03-10 08:55:58 -05:00
// lldbg-check:[...] 6
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 11:13:30 -05:00
// lldbr-check:(isize) *owned = 6
Use explicit LLDB commands instead of `print`/`p` aliases.
2024-03-15 09:05:57 -05:00
// lldb-command:v closure_local
Remove LLDB persistent results in `compiletest`.
2024-03-10 08:55:58 -05:00
// lldbg-check:[...] 8
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 11:13:30 -05:00
// lldbr-check:(isize) closure_local = 8
debuginfo: Add LLDB autotests to debuginfo test suite. This commit adds LLDB autotests to the test suite but does not activate them by default yet.
2014-07-09 07:46:09 -05:00
// lldb-command:continue
Fix closed over variables not available in debuginfo for Windows MSVC The issue was that the resulting debuginfo was too complex for LLVM to translate into CodeView records correctly. As a result, it simply ignored the debuginfo which meant Windows debuggers could not display any closed over variables when stepping inside a closure. This fixes that by spilling additional variables to the stack so that the resulting debuginfo is simple (just `*my_variable.dbg.spill`) and LLVM can generate the correct CV records.
2021-04-06 12:34:17 -05:00
// === CDB TESTS ===================================================================================
// cdb-command: g
// cdb-command: dx variable
// cdb-check:variable : 1 [Type: [...]]
// cdb-command: dx constant
// cdb-check:constant : 2 [Type: [...]]
// cdb-command: dx a_struct
// cdb-check:a_struct [Type: var_captured_in_nested_closure::Struct]
// cdb-check: [+0x[...]] a : -3 [Type: [...]]
// cdb-check: [+0x[...]] b : 4.500000 [Type: [...]]
// cdb-check: [+0x[...]] c : 0x5 [Type: unsigned [...]]
// cdb-command: dx struct_ref
// cdb-check:struct_ref : 0x[...] [Type: var_captured_in_nested_closure::Struct *]
// cdb-check: [+0x[...]] a : -3 [Type: [...]]
// cdb-check: [+0x[...]] b : 4.500000 [Type: [...]]
// cdb-check: [+0x[...]] c : 0x5 [Type: unsigned [...]]
// cdb-command: dx owned
// cdb-check:owned : 0x[...] : 6 [Type: [...] *]
// cdb-check: 6 [Type: [...]]
// cdb-command: dx closure_local
// cdb-check:closure_local : 8 [Type: [...]]
// cdb-command: dx nested_closure
debuginfo: Make sure that type names for closure and generator environments are unique in debuginfo. Before this change, closure/generator environments coming from different instantiations of the same generic function were all assigned the same name even though they were distinct types with potentially different data layout. Now we append the generic arguments of the originating function to the type name. This commit also emits '{closure_env#0}' as the name of these types in order to disambiguate them from the accompanying closure function '{closure#0}'. Previously both were assigned the same name.
2022-01-19 10:56:53 -06:00
// cdb-check:nested_closure [Type: var_captured_in_nested_closure::main::closure$0::closure_env$0]
Fix closed over variables not available in debuginfo for Windows MSVC The issue was that the resulting debuginfo was too complex for LLVM to translate into CodeView records correctly. As a result, it simply ignored the debuginfo which meant Windows debuggers could not display any closed over variables when stepping inside a closure. This fixes that by spilling additional variables to the stack so that the resulting debuginfo is simple (just `*my_variable.dbg.spill`) and LLVM can generate the correct CV records.
2021-04-06 12:34:17 -05:00
// cdb-command: g
// cdb-command: dx variable
// cdb-check:variable : 1 [Type: [...]]
// cdb-command: dx constant
// cdb-check:constant : 2 [Type: [...]]
// cdb-command: dx a_struct
// cdb-check:a_struct [Type: var_captured_in_nested_closure::Struct]
// cdb-check: [+0x[...]] a : -3 [Type: [...]]
// cdb-check: [+0x[...]] b : 4.500000 [Type: [...]]
// cdb-check: [+0x[...]] c : 0x5 [Type: unsigned [...]]
// cdb-command: dx struct_ref
// cdb-check:struct_ref : 0x[...] [Type: var_captured_in_nested_closure::Struct *]
// cdb-check: [+0x[...]] a : -3 [Type: [...]]
// cdb-check: [+0x[...]] b : 4.500000 [Type: [...]]
// cdb-check: [+0x[...]] c : 0x5 [Type: unsigned [...]]
// cdb-command: dx owned
// cdb-check:owned : 0x[...] : 6 [Type: [...] *]
// cdb-check: 6 [Type: [...]]
// cdb-command: dx closure_local
// cdb-check:closure_local : 8 [Type: [...]]
Update code with new lint names
2014-10-27 17:37:07 -05:00
#![allow(unused_variables)]
Feature-gate `#[no_debug]` and `#[omit_gdb_pretty_printer_section]` Closes #28091.
2015-09-19 15:33:47 -05:00
#![feature(omit_gdb_pretty_printer_section)]
debuginfo: Add a rust-gdb shell script that will start GDB with Rust pretty printers enabled.
2014-12-03 16:48:18 -06:00
#![omit_gdb_pretty_printer_section]
debuginfo: Added test cases for structs, tuples, enums, etc passed by value. Also updated documentation comments in debuginfo and renamed DebugContext to CrateDebugContext.
2013-08-29 04:44:11 -05:00
struct Struct {
Mass rename uint/int to usize/isize Now that support has been removed, all lingering use cases are renamed.
2015-03-25 19:06:52 -05:00
a: isize,
remove the `float` type It is simply defined as `f64` across every platform right now. A use case hasn't been presented for a `float` type defined as the highest precision floating point type implemented in hardware on the platform. Performance-wise, using the smallest precision correct for the use case greatly saves on cache space and allows for fitting more numbers into SSE/AVX registers. If there was a use case, this could be implemented as simply a type alias or a struct thanks to `#[cfg(...)]`. Closes #6592 The mailing list thread, for reference: https://mail.mozilla.org/pipermail/rust-dev/2013-July/004632.html
2013-09-26 01:26:09 -05:00
b: f64,
Mass rename uint/int to usize/isize Now that support has been removed, all lingering use cases are renamed.
2015-03-25 19:06:52 -05:00
c: usize
debuginfo: Added test cases for structs, tuples, enums, etc passed by value. Also updated documentation comments in debuginfo and renamed DebugContext to CrateDebugContext.
2013-08-29 04:44:11 -05:00
}
fn main() {
let mut variable = 1;
let constant = 2;
let a_struct = Struct {
a: -3,
b: 4.5,
c: 5
};
let struct_ref = &a_struct;
Remove box syntax from most places in src/test outside of the issues dir
2021-08-24 19:39:40 -05:00
let owned: Box<_> = Box::new(6);
debuginfo: Added test cases for structs, tuples, enums, etc passed by value. Also updated documentation comments in debuginfo and renamed DebugContext to CrateDebugContext.
2013-08-29 04:44:11 -05:00
debuginfo: argument and upvar names for MIR.
2016-04-16 13:51:26 -05:00
let mut closure = || {
debuginfo: Added test cases for structs, tuples, enums, etc passed by value. Also updated documentation comments in debuginfo and renamed DebugContext to CrateDebugContext.
2013-08-29 04:44:11 -05:00
let closure_local = 8;
debuginfo: argument and upvar names for MIR.
2016-04-16 13:51:26 -05:00
let mut nested_closure = || {
debuginfo: Add LLDB autotests to debuginfo test suite. This commit adds LLDB autotests to the test suite but does not activate them by default yet.
2014-07-09 07:46:09 -05:00
zzz(); // #break
tests: remove uses of Gc.
2014-10-02 00:10:09 -05:00
variable = constant + a_struct.a + struct_ref.a + *owned + closure_local;
debuginfo: Added test cases for structs, tuples, enums, etc passed by value. Also updated documentation comments in debuginfo and renamed DebugContext to CrateDebugContext.
2013-08-29 04:44:11 -05:00
};
debuginfo: Add LLDB autotests to debuginfo test suite. This commit adds LLDB autotests to the test suite but does not activate them by default yet.
2014-07-09 07:46:09 -05:00
zzz(); // #break
debuginfo: Added test cases for structs, tuples, enums, etc passed by value. Also updated documentation comments in debuginfo and renamed DebugContext to CrateDebugContext.
2013-08-29 04:44:11 -05:00
nested_closure();
};
closure();
}
fn zzz() {()}
Reference in New Issue Copy Permalink