we actually deliver MTasker timeouts with the wrong d_tid set. Unknown if this matter...

diff --git a/pdns/mtasker.cc b/pdns/mtasker.cc
index 605af28813470e954d2e4a92cc6a8c8734ac6fd0..f92685451bd445b10fbfc626ef62b02bf151fb6f 100644 (file)
--- a/pdns/mtasker.cc
+++ b/pdns/mtasker.cc
@@ -330,6 +330,7 @@ template<class Key, class Val>bool MTasker<Key,Val>::schedule(struct timeval*  n
         d_waitstatus=TimeOut;
         d_eventkey=i->key;        // pass waitEvent the exact key it was woken for
         ucontext_t* uc = i->context;
+        d_tid = i->tid;
         ttdindex.erase(i++);                  // removes the waitpoint 
 
         if(swapcontext(&d_kernel, uc)) { // swaps back to the above point 'A'