[MDEV-3502] LP:814238 - safe_mutex issues must be assertions in debug binary Created: 2011-07-21  Updated: 2015-02-02  Resolved: 2012-10-04

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Philip Stoev (Inactive) Assignee: Michael Widenius
Resolution: Fixed Votes: 0
Labels: Launchpad

Attachments: XML File LPexportBug814238.xml    

 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.

 Comments   
Comment by Michael Widenius [ 2011-07-26 ]

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.

Comment by Rasmus Johansson (Inactive) [ 2011-12-02 ]

Launchpad bug id: 814238

Generated at Thu Feb 08 06:49:06 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.