-
|
I'm attempting to analyse a large (~2500 source file) C++ project (see #3309 for background). I've got the CTU scanner running using clang-12, however I'm seeing a large number of clang errors of the form: See below for additional error message details. Is this a known issue / any workarounds possible - or should I raise a bug with llvm as directed to in the error message? |
Beta Was this translation helpful? Give feedback.
Answered by
martong
May 13, 2021
Replies: 3 comments 5 replies
-
|
This problem is related to the Clang Static Analyzer, so please raise a ticket on https://bugs.llvm.org/. Maybe @martong knows something about this problem, because he is contributing to the analyzer itself. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Thank you for the report! The import of a Normally an unsupported node shouldn't result in a crash, but most probably there is another error which happens when our clean up mechanism - to handle the unsupported AST node - kicks in. That is a known problem and we are working on that. |
Beta Was this translation helpful? Give feedback.
4 replies
-
|
@martong Thanks for the quick response. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, the crash is probably caused by the null pointer dereference. diff --git a/clang/lib/AST/ASTImporter.cpp b/clang/lib/AST/ASTImporter.cpp
index dd11e3662148..9caa1178c0b7 100644
--- a/clang/lib/AST/ASTImporter.cpp
+++ b/clang/lib/AST/ASTImporter.cpp
@@ -8383,7 +8383,11 @@ Expected<Decl *> ASTImporter::Import(Decl *FromD) {
// traverse of the 'to' context).
auto PosF = ImportedFromDecls.find(ToD);
if (PosF != ImportedFromDecls.end()) {
- SharedState->removeDeclFromLookup(ToD);
+ // In the case of TypedefNameDecl we create the Decl first and only
+ // then we import and set its DeclContext. So, the DC might not be set
+ // when we reach here.
+ if (ToD->getDeclContext())
+ SharedState->removeDeclFromLookup(ToD);
ImportedFromDecls.erase(PosF);
}
|
Beta Was this translation helpful? Give feedback.
-
|
Thank you. I’ll give that a go - probably next week now. |
Beta Was this translation helpful? Give feedback.
-
|
The fix landed upstream, llvm/llvm-project@88ee91c. |
Beta Was this translation helpful? Give feedback.
Answer selected by
daverigby
-
|
The other one is still under review: |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Landed at May 18, llvm/llvm-project@88ee91c. |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Thank you for the report!
The import of a
Bindingis not yet implemented in theASTImporter.I am taking this issue to our internal tracker and will come back to here once we implement it.
Normally an unsupported node shouldn't result in a crash, but most probably there is another error which happens when our clean up mechanism - to handle the unsupported AST node - kicks in. That is a known problem and we are working on that.