Disable 'not' test on Windows because 'env' from GnuWin32 cannot be used without arguments.
[not][test] Fix disable-symbolization.test when 'printenv' is not availableOn Windows, 'env' or 'printenv' may not exist.Also switch back to 'env' which is specified by POSIX.1-2017. 'printenv' i
[not][test] Fix disable-symbolization.test when 'printenv' is not availableOn Windows, 'env' or 'printenv' may not exist.Also switch back to 'env' which is specified by POSIX.1-2017. 'printenv' is notstandard (I picked it because 'printenv' exists on GnuWin32 but 'env' does not).Reviewed By: zequanwuDifferential Revision: https://reviews.llvm.org/D86496
show more ...
PrintStackTrace: don't symbolize if LLVM_DISABLE_SYMBOLIZATION is setSee http://lists.llvm.org/pipermail/llvm-dev/2017-June/113975.html for a related previous discussion.Many tools install signal
PrintStackTrace: don't symbolize if LLVM_DISABLE_SYMBOLIZATION is setSee http://lists.llvm.org/pipermail/llvm-dev/2017-June/113975.html for a related previous discussion.Many tools install signal handlers to print stack traces and optionallysymbolize the addresses with an external program 'llvm-symbolizer' (whensearching for 'llvm-symbolizer', the directory containg the executableis preferred over PATH).'llvm-symbolizer' can be slow if the executable is large and/or ifllvm-symbolizer' itself is under-optimized. For example, my 'llvm-lto2' from a-DCMAKE_BUILD_TYPE=Debug build is 443MiB. The 'llvm-symbolizer' from the samebuild takes ~2s to symbolize it. (An optimized 'llvm-symbolizer' takes 0.34s).A crashed clang may take more than 5s to symbolize a stack trace.If a test file has several `not --crash` RUN lines. It can be very slow in a Debug build.This patch makes `not --crash` set an environment variable to suppress symbolization.This is similar to D33804 which uses a command line option.I pick 'symbolization' instead of 'symbolication' because the former isused much more commonly and its stem matches 'llvm-symbolizer'.Also set LLVM_DISABLE_CRASH_REPORT=1, which is currently only applicable on`__APPLE__`.Reviewed By: dblaikie, aganeaDifferential Revision: https://reviews.llvm.org/D86170