 |
 |
In Lukasz's example, the thread holding the lock is no longer there. So, it would seem that the thread was cancelled while it was holding that lock. I can't do anything about that. The thread should not have been cancelled. In Andreas' second example, had he gone to thread 253 and printed out the lock information for *that* thread he would have likely seen that the thread holding the lock which 253 is waiting for is gone as well. Both the timeout queue lock and the callback lock are recursive so no problem with multiple locking by the same thread. So, who is cancelling these threads? Certainly not the poller. --- Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/4#issuecomment-16324315 ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the XROOTD-DEV list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1