In QNamePool::remove() there is this code:

// Tail call. Should avoid deadlock because no new stack frame.

Even if this is not an out-right bug, i think it is dangerous to reply on 
tail-recursion optimization of the underlying compiler. 

I understand that the current trunk code has the same problem.  

Do you want to fix it, i.e. release the lock before calling 

Your team Zorba Coders is subscribed to branch lp:zorba.

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to