Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:
Description
All safe_mutex warnings must cause assertions in a debug binary. If they are simply reported in the error log with no other indication, they are very difficult to detect in an automatic test.
Gliffy Diagrams
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
Re: safe_mutex issues must be assertions in debug binary
Personally I don't want to have an assert here, as I prefer to get all mutex error warnings collected instead of getting a crash.
I have however added a new option --debug-assert-on-error, which should be used by automatic tests that wants asserts for things like this.
Setting this new variable also sets --debug-assert-if-crashed-table.