safe_mutex issues must be assertions in debug binary
Bug #814238 reported by
Philip Stoev
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MariaDB |
Fix Released
|
Medium
|
Michael Widenius |
Bug 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.
Changed in maria: | |
milestone: | none → 5.2 |
assignee: | nobody → Michael Widenius (monty) |
Changed in maria: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
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. assert- on-error, which should be used by automatic tests that wants asserts for things like this. assert- if-crashed- table.
I have however added a new option --debug-
Setting this new variable also sets --debug-