Replacing ZERO_MUTEX_INITIALIZER with TOKU_MUTEX_INITIALIZER is wrong for debug builds

Description

replaced ZERO_MUTEX_INITIALIZER with TOKU_MUTEX_INITIALIZER and ZERO_COND_INITIALIZER with TOKU_COND_INITIALIZER to fix compiler warnings.

This is incorrect: TOKU_ initialisers produce immediately usable mutex/cond, while ZERO_ ones produce uninitialised ones. The differences becomes apparent on toku_mutex_init which checks that the mutex is uninitialised ones.

The fix is to revert this bit of and then deal with warnings properly later.

Environment

None

Activity

Show:
Laurynas Biveinis
September 10, 2015, 7:59 AM
Fixed

Assignee

Laurynas Biveinis

Reporter

Laurynas Biveinis

Labels

None

External issue ID

None

Freshdesk Tickets

None

Fix versions

Priority

Blocker