Displaying 3 results from an estimated 3 matches for "8a7b12eb42012990ba534787c4a47275".
2020 Feb 26
2
Why is lldb telling me "variable not available"?
...unning into the limitations of how far I can get here by
> hacking up the LLVM IR directly, but I've made a couple of tries here
> without any luck. I put the IR files and the DWARF dumps of
> executables built from that IR in another GitHub gist,
> https://gist.github.com/modocache/8a7b12eb42012990ba534787c4a47275 <https://gist.github.com/modocache/8a7b12eb42012990ba534787c4a47275>.
> Here's a summary of the attempts I've made -- all of them with your
> patch included in my llvm-project tree:
>
> 1. Don't lower llvm.dbg.declare to llvm.dbg.value at all, no other
> changes --...
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"?
...tations of how far I can get here by
> > hacking up the LLVM IR directly, but I've made a couple of tries here
> > without any luck. I put the IR files and the DWARF dumps of
> > executables built from that IR in another GitHub gist,
> > https://gist.github.com/modocache/8a7b12eb42012990ba534787c4a47275.
> > Here's a summary of the attempts I've made -- all of them with your
> > patch included in my llvm-project tree:
> >
> > 1. Don't lower llvm.dbg.declare to llvm.dbg.value at all, no other
> > changes -- doesn't work, in the way I expected it to not...