Displaying 2 results from an estimated 2 matches for "addr66".
Did you mean:
addr16
2020 Feb 12
2
Why is lldb telling me "variable not available"?
...g !661
> %inc19 = add nsw i32 %15, 1, !dbg !670
> call void @llvm.dbg.value(metadata i32 %inc19, metadata !659,
> metadata !DIExpression()), !dbg !661
> store i32 %inc19, i32* %i.reload.addr62, align 4, !dbg !670
>
> Could have a call to llvm.dbg.addr(metadata i32 *%i.reload.addr66,
> ...) inserted after the store, indicating that the variable is located
> in memory. This should work (TM) so long as that memory is never
> overwritten with something that isn't the current value of "i" on
> every path after the call to llvm.dbg.addr; and on every path...
2020 Feb 06
2
Why is lldb telling me "variable not available"?
Hi all, I’m working on improving the debugging experience for C++20
coroutines when compiled with LLVM/Clang, and I could use some help
from someone who understands debug information and DWARF (knowledge of
coroutines isn't necessary, I don't think).
Specifically, I’m trying to improve lldb’s behavior when showing
variables in the current stack frame, when that frame corresponds to a