Re: [lldb-dev] Hiding local variables not defined yet

> >> >> >> On Apr 9, 2021, at 11:39 AM, Emre Kultursay via lldb-dev < >> lldb-dev@lists.llvm.org> wrote: >> >> When debugging C/C++ (statically scoped languages), does LLDB recognize >> (or does it have a setting for it) that a local variable i

Re: [lldb-dev] Hiding local variables not defined yet

E (I'm looking at Android Studio). Thanks for the explanation and also the details about the compiler provided info. On Fri, Apr 9, 2021 at 10:15 PM Greg Clayton wrote: > > > On Apr 9, 2021, at 11:39 AM, Emre Kultursay via lldb-dev < > lldb-dev@lists.llvm.org> wrote: > > Wh

[lldb-dev] Hiding local variables not defined yet

When debugging C/C++ (statically scoped languages), does LLDB recognize (or does it have a setting for it) that a local variable is not defined yet at the current program address (i.e., DW_AT_decl_line is less than the source line for the address), and thus, not include it in the list of locals

Re: [lldb-dev] Is there a just-my-code like debugging mode for LLDB?

; > Greg > > On May 8, 2020, at 9:07 AM, Emre Kultursay via lldb-dev < > lldb-dev@lists.llvm.org> wrote: > > Hi lldb-dev, > > *TL;DR: *Has there been any efforts to introduce something like "Just My > Code" debugging on LLDB? Debugging on Android would really bene

[lldb-dev] Is there a just-my-code like debugging mode for LLDB?

Hi lldb-dev, *TL;DR: *Has there been any efforts to introduce something like "Just My Code" debugging on LLDB? Debugging on Android would really benefit from this. *Details:* Native Android apps typically have a single .so file from the user, but load ~150 system libraries. When attaching LLDB

[lldb-dev] How to associate a bug and CL?

llvm-project dev noob here. I opened a Bug and have some CLs to fix them. How do I link the CL with the bug so that the code reviewer sees what bug I'm fixing? ___ lldb-dev