Re: [lldb-dev] [llvm-dev] Why is lldb telling me "variable not available"?

2020-02-26 Thread Vedant Kumar via lldb-dev
> On Feb 26, 2020, at 3:29 PM, Brian Gesiak via lldb-dev > wrote: > > Vedant, Jeremy, > > Thanks a ton! I copied ASan's use of 'replaceDbgDeclare', think that worked! > > https://github.com/modocache/llvm-project/commit/afbc04e1dcba has some > extremely quick and dirty changes I made (with

Re: [lldb-dev] [llvm-dev] Why is lldb telling me "variable not available"?

2020-02-26 Thread Brian Gesiak via lldb-dev
Vedant, Jeremy, Thanks a ton! I copied ASan's use of 'replaceDbgDeclare', think that worked! https://github.com/modocache/llvm-project/commit/afbc04e1dcba has some extremely quick and dirty changes I made (with no tests!), and a link to a Gist with the LLVM IR and DWARF produced,

Re: [lldb-dev] [llvm-dev] Why is lldb telling me "variable not available"?

2020-02-26 Thread Brian Gesiak via lldb-dev
Vedant, thank you! I had meant to ask if any of this reminded you all of something else that I could emulate. I'll look into uses of 'replaceDbgDeclare' in SafeStack/ASan. - Brian On Wed, Feb 26, 2020 at 5:08 PM Vedant Kumar wrote: > > I haven't fully parsed this thread (sorry!), but I wanted to

Re: [lldb-dev] [llvm-dev] Why is lldb telling me "variable not available"?

2020-02-26 Thread Vedant Kumar via lldb-dev
I haven't fully parsed this thread (sorry!), but I wanted to briefly mention that the SafeStack & ASan passes both do something similar (I think): move local variables backed by allocas onto a separate stack. These passes use replaceDbgDeclare to rewrite dbg.declares s.t. they point into the

Re: [lldb-dev] [llvm-dev] Why is lldb telling me "variable not available"?

2020-02-26 Thread Brian Gesiak via lldb-dev
Awesome, thanks Jeremy. On Wed, Feb 26, 2020 at 11:02 AM Jeremy Morse wrote: > > Hi Brian, > > On Tue, Feb 25, 2020 at 7:43 PM Brian Gesiak 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 > >

Re: [lldb-dev] [llvm-dev] Why is lldb telling me "variable not available"?

2020-02-26 Thread Jeremy Morse via lldb-dev
Hi Brian, On Tue, Feb 25, 2020 at 7:43 PM Brian Gesiak 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

[lldb-dev] [10.0.0 Release] We're behind schedule

2020-02-26 Thread Hans Wennborg via lldb-dev
Hello everyone, Today was the scheduled day for the final release tag, but the release is not ready yet. There are still a bunch of open blockers at https://llvm.org/PR44555 Any help on these is very much appreciated. My ambition is to get most of these fixed by the end of the week, tag RC3,

[lldb-dev] Is bitcast breaking lldb a bug?

2020-02-26 Thread Levo DeLellis via lldb-dev
This feels like a bug to me. Yesterday I was asking what the rules were because it felt like things change and break randomly. Now I have a good example. (link to my email yesterday http://lists.llvm.org/pipermail/lldb-dev/2020-February/015989.html) Take this example source file int main() {