The SourceLocation of the decl node related to macro extension is invalid. How to obtain the file and line number information according to the decl node?

[yaqianp]

example:

bool ClangASTVisitor::TraverseDecl(clang::Decl* decl)
{
    if (decl == nullptr) {
        return true;
    }
    if (auto* cxxRecordDecl = llvm::dyn_cast<clang::CXXRecordDecl>(decl);
        IsTemplateCXXRecordUninstantiated(cxxRecordDecl)) {
        return true;
    }
    const std::string& currFilename =
        m_astContext->getSourceManager().getFilename(decl->getEndLoc()).str();

    if (decl->getBeginLoc().isInvalid()) {
     // How to obtain the file and line number information according to the decl node?
   }

}

[DeinAlptraum]

Hi, I'm not entirely sure I understood your question correctly, but when using libclang, you're processing an AST representation of the code, which has already passed through the preprocessor, i.e. all macros have already been expanded. So you'll never see e.g. AAA, just struct M {int a;};

[yaqianp]

Hi, I'm not entirely sure I understood your question correctly, but when using libclang, you're processing an AST representation of the code, which has already passed through the preprocessor, i.e. all macros have already been expanded. So you'll never see e.g. AAA, just struct M {int a;};

Appreciate your reply, It is worth noting that first I use libtooling, and then after the Clang AST is generated, you can view the source code information through dump. It's an oolong incident. I've found a solution. First, SourceLocation is valid. Then, use the isMacroID interface to determine whether SourceLocation is a macro ID. If yes, i can use the getExpansionLoc interface to obtain the source code information.

[DeinAlptraum]

@yaqianp okay, glad to hear! Can I close this issue then?