Build with UNIV_DEBUG causes asserts

[Seppo Jaakola]

It turns out that build with UNIV_DEBUG defined, causes assert(s).

At least in loc0lock.c:lock_rec_add_to_queue():
 ut_ad((type_mode & (LOCK_WAIT | LOCK_GAP))
       || ((type_mode & LOCK_MODE_MASK) != LOCK_X)
       || !lock_rec_other_has_expl_req(LOCK_S, 0, LOCK_WAIT,
           rec, trx));

,where lock_rec_other_has_expl_req ... asserts

[Seppo Jaakola (seppo-jaakola)]

wsrep code path does not cancel the waiting, if victim is in waiting state.
This is because we want to control that victim does no leave, before we put our lock in the lock queue.
This change in locking protocol caused the assert to fail.

[Seppo Jaakola (seppo-jaakola)]

Current trunk (0.7pre RC) passes with UNIV_DEBUG build. Tested with two nodes and conflicting sqlgen load.