Compile this code with `-Copt-level=0`: ``` rust #[inline(never)] fn zzz() {} #[inline(always)] fn inlined_fn() { let a = 1; zzz(); // #break } fn main() { inlined_fn(); } ``` In LLDB, set a breakpoint on line 8, then run the program. After breaking, type `print a`'. Result: ``` error: use of undeclared identifier 'a' error: 1 error parsing expression ``` Interestingly, the `frame variable` command shows the expected value: `(int) a = 1`. Meta: LLDB version: lldb-360.1.25 (OSX XCode 8) Rustc version: rustc 1.10.0 (cfcb716cf 2016-07-03) x86_64-apple-darwin
Activity
vadimcn commentedon Aug 8, 2016
Note: this is very likely an LLDB bug, because an equivalent C++ code exhibits the same behavior.
The extra lexical scope in
inlined_fnis important - without it, evaluation produces the correct result:(int) $0 = 1GDB works correctly.
michaelwoerister commentedon Aug 8, 2016
That makes me sad
:(Mark-Simulacrum commentedon May 14, 2017
So if this is an LLDB bug, then it seems like there's no use in us tracking it. As such, I'm going to close.