Displaying 3 results from an estimated 3 matches for "l3711".
Did you mean:
3711
2020 Feb 26
2
Why is lldb telling me "variable not available"?
...; expression 1>:1:1: use of undeclared identifier 'i''. This fits my
> mental model, I think: 'i' was declared in the function 'foo', and its
> DWARF information
> https://gist.github.com/modocache/8a7b12eb42012990ba534787c4a47275#file-repro-declare-dwarf-txt-L3711 <https://gist.github.com/modocache/8a7b12eb42012990ba534787c4a47275#file-repro-declare-dwarf-txt-L3711>
> only specifies its offset from the 'foo' frame. After the suspend
> point, lldb is stopped in 'foo.resume', and the 'foo' frame is no
> longer active, so...
2020 Feb 26
2
Why is lldb telling me "variable not available"?
Hi Brian,
On Tue, Feb 25, 2020 at 7:43 PM Brian Gesiak <modocache at gmail.com> wrote:
> In other words, the value of %i is stored on the frame object, on the
> heap, at an offset of 7 into the frame. I'm beginning to think a
> fundamental fix for this issue would be to stop replacing
> llvm.dbg.declare with llvm.dbg.value, and instead replace the
> llvm.dbg.declare with
2020 Feb 26
2
Why is lldb telling me "variable not available"?
...gt;:1:1: use of undeclared identifier 'i''. This fits my
> > mental model, I think: 'i' was declared in the function 'foo', and its
> > DWARF information
> > https://gist.github.com/modocache/8a7b12eb42012990ba534787c4a47275#file-repro-declare-dwarf-txt-L3711
> > only specifies its offset from the 'foo' frame. After the suspend
> > point, lldb is stopped in 'foo.resume', and the 'foo' frame is no
> > longer active, so lldb determines 'i' is out of scope. Makes sense!
> >
> > 2. Don't lowe...