3c95bdf9fa
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.
5 lines
156 B
Plaintext
5 lines
156 B
Plaintext
# 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}}
|