So, in particular, it looks like kdb5_util is acquiring a lock from 0 to bignum that fails, acquiring a lock from 0 to 0 that succeeds, releasing the lock from 0 to bignum (which succeeds?), and then while still holding the lock from 0 to 0 tries to get another lock from 0 to bignum. At least that's what it looks like if I'm reading that correctly.
I don't know what the significance of 6950411022381350912 I wonder if that's uninitialized memory of some kind.
