lldb/test/Shell/Error/assert.test

# REQUIRES: asserts
# RUN: not --crash lldb-test assert > %t.error 2>&1
# RUN: cat %t.error | FileCheck %s
# CHECK: {{lldb_assert failed|lldb-test assert}}
[lldb] Call os_log_fault on lldb_assert Call `os_log_fault` when an lldb assert fails. We piggyback off `LLVM_SUPPORT_XCODE_SIGNPOSTS`, which also depends on `os_log`, to avoid having to introduce another CMake check and corresponding define. This patch also adds a small test using lldb-test that verifies we abort with a "regular" assertion when asserts are enabled. Differential revision: https://reviews.llvm.org/D98987 2021-03-19 14:20:26 -07:00			`# REQUIRES: asserts`
			`# RUN: not --crash lldb-test assert > %t.error 2>&1`
			`# RUN: cat %t.error \| FileCheck %s`
[lldb] Don't search for system specific strings in assert.test Commit 6bc1e69de270db8d7191200f54158e4192f997ba changed the search string to also check for the generated strings that surround the plain assert: Assertion `false && "lldb-test assert"' failed ^^^^^^^^^ This causes the test to fail on setups where the generated assert message looks different. E.g., on macOS the generated message looks like this: Assertion failed: (false && "lldb_assert failed"), function lldb_assert This reverts the old behaviour of just checking for the actual string we have inside LLDB. 2021-03-29 10:39:10 +02:00			`# CHECK: {{lldb_assert failed\|lldb-test assert}}`