From fdd695c35c271bd467fd9da8a67589d733443c67 Mon Sep 17 00:00:00 2001 From: Nikolai Kosjar Date: Fri, 2 Feb 2018 15:18:40 +0100 Subject: Clang: Disable crash recovery in libclang ...because 1. We already run in a separate process. 2. It's not entirely clear in which state we end up after a crash, except for: 3. A "crashed" translation unit won't be freed, even when calling clang_disposeTranslationUnit(). This avoids undefined behavior within clangbackend and accumulated leaking memory in the long run. On the other side, crashes within libclang will crash clangbackend now, too. Change-Id: I0789c52db08ace2f7e181e3b7bdfc9f595f75e8d Reviewed-by: Ivan Donchevskii --- src/tools/clangbackend/clangbackendmain.cpp | 1 - 1 file changed, 1 deletion(-) (limited to 'src/tools/clangbackend/clangbackendmain.cpp') diff --git a/src/tools/clangbackend/clangbackendmain.cpp b/src/tools/clangbackend/clangbackendmain.cpp index 28b7f251b6..338fec7982 100644 --- a/src/tools/clangbackend/clangbackendmain.cpp +++ b/src/tools/clangbackend/clangbackendmain.cpp @@ -82,7 +82,6 @@ int main(int argc, char *argv[]) const QString connection = processArguments(application); - clang_toggleCrashRecovery(true); clang_enableStackTraces(); ClangCodeModelServer clangCodeModelServer; -- cgit v1.2.1