diff options
| author | Jonas Devlieghere <jonas@devlieghere.com> | 2019-07-05 21:22:54 +0000 |
|---|---|---|
| committer | Jonas Devlieghere <jonas@devlieghere.com> | 2019-07-05 21:22:54 +0000 |
| commit | b0fc4d470f4ccc98dd4deea5f64f646a279d28c4 (patch) | |
| tree | c507e0e8a2cb8b4191a45b3120c28f490d78316d /llvm/lib/Support/FileCheck.cpp | |
| parent | 5e9610a3f509c413a5c8978f94cd222f1bbb7e5d (diff) | |
| download | llvm-b0fc4d470f4ccc98dd4deea5f64f646a279d28c4.zip llvm-b0fc4d470f4ccc98dd4deea5f64f646a279d28c4.tar.gz llvm-b0fc4d470f4ccc98dd4deea5f64f646a279d28c4.tar.bz2 | |
lldb_assert: abort when assertions are enabled.
We had a long discussion in D59911 about lldb_assert and what it means.
The result was the assert manifesto on lldb.llvm.org.
> LLDB provides lldb_assert() as a soft alternative to cover the middle
> ground of situations that indicate a recoverable bug in LLDB. In a
> Debug configuration lldb_assert() behaves like assert(). In a Release
> configuration it will print a warning and encourage the user to file a
> bug report, similar to LLVM’s crash handler, and then return
> execution.
However, currently lldb_assert doesn't behave they way it's being
described there: it doesn't abort in a debug/assert build. This patch
fixes that by adding a call to assert() in lldb_assert().
Differential revision: https://reviews.llvm.org/D64267#1571962
llvm-svn: 365246
Diffstat (limited to 'llvm/lib/Support/FileCheck.cpp')
0 files changed, 0 insertions, 0 deletions