> On Apr 12, 2021, at 4:44 PM, Emre Kultursay wrote:
>
> Looking at Android Studio implementation a little deeper, it actually does
> the filtering the way I described in my first email, by comparing line
> numbers. It does not use the location expressions.
Interesting if they are doing
Looking at Android Studio implementation a little deeper, it actually does
the filtering the way I described in my first email, by comparing line
numbers. It does not use the location expressions.
Do you have a pointer to another implementation (e.g., lldb-vscode) that
filters based on location
>
> LLDB does only show variables that are in lexical scope in ...
Ah, yes, I got confused because I thought this filter was implemented
inside LLDB, yet the `frame variable` command was returning me all local
variables; I now notice that it's a filter that's implemented inside the
IDE (I'm
> On Apr 9, 2021, at 11:39 AM, Emre Kultursay via lldb-dev
> wrote:
>
> 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
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
