With DWARFv5, C++ static data members are represented as `DW_TAG_variable`s (see `faa3a5ea9ae481da757dab1c95c589e2d5645982`). In GetClangDeclForDIE, when trying to parse the `DW_AT_specification` that a static data member's CU-level `DW_TAG_variable` points to, we would try to `CreateVariableDeclaration`. Whereas previously it was a no-op (for `DW_TAG_member`s). However, adding `VarDecls` to RecordDecls for static data members should always be done in `CreateStaticMemberVariable`. The test-case is an exapmle where we would crash if we tried to create a `VarDecl` from within `GetClangDeclForDIE` for a static data member. This patch simply checks whether the `DW_TAG_variable` being parsed is a static data member, and if so, trivially returns from `GetClangDeclForDIE` (as we previously did for `DW_TAG_member`s).
25 lines
896 B
Plaintext
25 lines
896 B
Plaintext
# In DWARFv5, C++ static data members are represented
|
|
# as DW_TAG_variable. We make sure LLDB's expression
|
|
# evaluator doesn't crash when trying to parse such
|
|
# a DW_TAG_variable DIE, whose parent DIE is only
|
|
# a forward declaration.
|
|
|
|
# RUN: %clangxx_host %S/Inputs/dwo-static-data-member.cpp \
|
|
# RUN: -g -gdwarf-5 -gsplit-dwarf -flimit-debug-info -o %t
|
|
# RUN: %lldb %t -s %s -o exit 2>&1 | FileCheck %s
|
|
|
|
breakpoint set -n main
|
|
process launch
|
|
|
|
# CHECK: Process {{.*}} stopped
|
|
|
|
# FIXME: The expression evaluator tries to attach
|
|
# the static member's VarDecl to the NoCtor RecordDecl
|
|
# before passing the AST to clang; this requires the
|
|
# RecordDecl to be a full definition. But the debug-info
|
|
# only contains forward declaration for NoCtor. So
|
|
# LLDB fails to evaluate the expression.
|
|
expression NoCtor::i
|
|
# CHECK-LABEL: expression NoCtor::i
|
|
# CHECK: use of undeclared identifier 'NoCtor'
|