4 Commits

Author	SHA1	Message	Date
Serge Pavlov	a693b907c7	Do not run tests for crash recovery if libstdc++ safe mode is enabled ... If expensive checks are enabled, safe mode of libstdc++ is enabled too. In this mode the library uses more complex data that allow additional checks, for instance, a container may keep list of iterators that points to it. If a code crashes it can leave these complex library objects in inconsistent state. It occurs in a few tests that check error recovery if compiler crashes. These test hang in expensive check mode, as the library tries to synchronize access to the iterators pointing to some container, but corresponding mutex remains locked after the crash. This fix marks these tests as unsupported if clang is built with libstdc++ safe mode enabled. Differential Revision: https://reviews.llvm.org/D31126 llvm-svn: 300392	2017-04-15 05:53:49 +00:00
Argyrios Kyrtzidis	50126f1259	[libclang] Make sure we don't access past the tokens buffer while token annotation. ... Also disable crash recovery using 'LIBCLANG_DISABLE_CRASH_RECOVERY' environment variable. llvm-svn: 195819	2013-11-27 05:50:55 +00:00
Daniel Dunbar	b44eb0b900	tests: Use REQUIRES: instead of XFAIL: for crash recovery tests; running them on ... Windows breaks things (because it pops up dialogs) since we don't have crash recovery support there (yet). llvm-svn: 111970	2010-08-24 21:39:55 +00:00
Daniel Dunbar	583c3b775e	libclang: Put clang_parseTranslationUnit inside a crash recovery context. ... llvm-svn: 111387	2010-08-18 18:43:17 +00:00