Details
- Reviewers
JDevlieghere teemperor - Group Reviewers
Restricted Project - Commits
- rG4d46fde67908: Terminate debugger if an assert was hit
rL341387: Terminate debugger if an assert was hit
rLLDB341387: Terminate debugger if an assert was hit
Diff Detail
Event Timeline
| source/Utility/LLDBAssert.cpp | ||
|---|---|---|
| 21–22 | I guess while we're at it we can turn this into an early return and use LLVM_LIKELY? if (LLVM_LIKELY(expression))
return; | |
| source/Utility/LLDBAssert.cpp | ||
|---|---|---|
| 21–22 | I thought about it also.. :) I will update the patch. | |
| source/Utility/LLDBAssert.cpp | ||
|---|---|---|
| 31 | abort() may be a better choice here (exit() path calls a lot of shutdown code and it's not safe in a number of cases) | |
Yes abort is better as exit will cause the global C++ destructor chain to be called. I was always thinking lldbassert() was aborting, but seeing as this is not the case this could cause problems if you enable it as it will be a change. Watch the buildbots carefully.
If you include the text:
Differential Revision: https://reviews.llvm.org/D51604
It will automatically close this and put in a comment with the revision
I guess while we're at it we can turn this into an early return and use LLVM_LIKELY?
if (LLVM_LIKELY(expression)) return;