While evaluating expressions when stopped in a class method, there was a
problem of member variables hiding local variables. This was happening
because, in the context of a method, clang already knew about member
variables with their name and assumed that they were the only variables
with those names in scope. Consequently, clang never checks with LLDB
about the possibility of local variables with the same name and goes
wrong. This change addresses the problem by using an artificial
namespace "$lldb_local_vars". All local variables in scope are
declared in the "$lldb_expr" method as follows:
using $__lldb_local_vars::<local var 1>; using $__lldb_local_vars::<local var 2>; ...
This hides the member variables with the same name and forces clang to
enquire about the variables which it thinks are declared in
$lldb_local_vars. When LLDB notices that clang is enquiring about
variables in $lldb_local_vars, it looks up local vars and conveys
their information if found. This way, member variables do not hide local
variables, leading to correct evaluation of expressions.
A point to keep in mind is that the above solution does not solve the
problem for one specific case:
namespace N
{
int a;
}
class A
{
public:
void Method();
int a;
};
void
A::Method()
{
using N::a;
...
// Since the above solution only touches locals, it does not
// force clang to enquire about "a" coming from namespace N.
}
I think we should do this in all C++ cases. The reason is because it'll make sure the method gets more testing and if anything fails we'll catch it in the common case instead of seeing it only in specific "edge" cases. Could we just check if the frame is C++?