aboutsummaryrefslogtreecommitdiff
path: root/lldb/source/Plugins/ScriptInterpreter/Python/PythonReadline.h
diff options
context:
space:
mode:
authorTimur Golubovich <timur.golubovich@syntacore.com>2025-10-29 15:13:34 +0300
committerGitHub <noreply@github.com>2025-10-29 12:13:34 +0000
commit4dfe212dade71e0e4e5ea4609e403f5e523eeb74 (patch)
treefc871000e726cc0f2df1f53c357b217e560f9bbb /lldb/source/Plugins/ScriptInterpreter/Python/PythonReadline.h
parent31180ba0720a8fdf030881229c6ca84b79c558d7 (diff)
downloadllvm-4dfe212dade71e0e4e5ea4609e403f5e523eeb74.zip
llvm-4dfe212dade71e0e4e5ea4609e403f5e523eeb74.tar.gz
llvm-4dfe212dade71e0e4e5ea4609e403f5e523eeb74.tar.bz2
[lldb][DWARFASTParserClang] Added a check for the specialization existence (#154123)
[lldb][DWARFASTParserClang] Added a check for the specialization existence While debugging an application with incorrect dwarf information, where DW_TAG_template_value_parameter was lost, I found that lldb does not check that the corresponding specialization exists. As a result, at the stage when ASTImporter works, the type is completed in such a way that it inherits from itself. And during the calculation of layout, an infinite recursion occurs. To catch this error, I added a corresponding check at the stage of restoring the type from dwarf information. I also added a trivial assert in clang to check that the class does not inherit from itself.
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/PythonReadline.h')
0 files changed, 0 insertions, 0 deletions