History log of /external/clang/test/Parser/crash-report.c
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
b7a5120f9dbc87b026233eb9e8a00be636265d0c 05-Jul-2013 Rafael Espindola <rafael.espindola@gmail.com> Use the new --crash option in commands that are expected to crash.

git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@185679 91177308-0d34-0410-b5e6-96231b3b80d8
/external/clang/test/Parser/crash-report.c
96e7813f08c6adf1d8657b0da86741b54e850fd7 04-Jul-2013 Rafael Espindola <rafael.espindola@gmail.com> Add 'not' to commands that are expected to fail.

This is at least good documentation, but also opens the possibility of
using pipefail.

git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@185652 91177308-0d34-0410-b5e6-96231b3b80d8
/external/clang/test/Parser/crash-report.c
cdd81e5a68cefd5ba057f1f638f31a3ec6ace18d 25-Mar-2013 Nick Lewycky <nicholas@mxc.ca> Try harder to be signal-safe inside our signal handler. The most prominent behavioural
difference is that we no longer clean the token before emitting it. This fixes a bug where
clang hangs in the middle of crashing because the crash handler calls malloc from inside
a crash that happened inside of free.


git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@177919 91177308-0d34-0410-b5e6-96231b3b80d8
/external/clang/test/Parser/crash-report.c