[lldb-dev] [Bug 49946] New: python SBTarget.EvaluateExpression cannot call selectors prefixed with underscore

2021-04-12 Thread via lldb-dev
https://bugs.llvm.org/show_bug.cgi?id=49946 Bug ID: 49946 Summary: python SBTarget.EvaluateExpression cannot call selectors prefixed with underscore Product: lldb Version: unspecified Hardware: PC OS: All

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

2021-04-12 Thread Emre Kultursay via lldb-dev
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 e

[lldb-dev] [Bug 49941] New: register commands require a frame unconditionally

2021-04-12 Thread via lldb-dev
https://bugs.llvm.org/show_bug.cgi?id=49941 Bug ID: 49941 Summary: register commands require a frame unconditionally Product: lldb Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: normal

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

2021-04-12 Thread Emre Kultursay via lldb-dev
> > 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 lookin