[cfe-dev] how to tolerate the assertion failures in llvm and clang

[alan snape via cfe-dev]

My team is developing a static analysis tool based on clang and llvm, but
the assertion failures in the source code of llvm and clang will always
crash the program execution, which is not acceptable in a **stable
product**. The tool analyzes the functions one by one in the Call Graph SCC
order, so is there any way to tolerate the assertion failures and continue
the analysis on the next function when assertion failures occur on calling
some APIs of clang and llvm? (crashes only the analysis of the function (the
analysis methods of the FunctionDecl) being analyzed, not the entire
program)

Thanks,
Ella
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20180624/2d9fd1de/attachment.html>