 |
 |
I managed to carry out the scenario I described in my previous comment (which was rather tricky) and indeed it resulted in double delete of the incoming response. The backtrace is quite similar, but not exactly the same: #0 0x00007ffff7b5fa23 in ~XRootDMsgHandler (this=0x60c350, __in_chrg=<optimized out>) at /home/simonm/git/xrootd/src/./XrdCl/XrdClXRootDMsgHandler.hh:104 #1 XrdCl::XRootDMsgHandler::~XRootDMsgHandler (this=0x60c350, __in_chrg=<optimized out>) at /home/simonm/git/xrootd/src/./XrdCl/XrdClXRootDMsgHandler.hh:108 #2 0x00007ffff7b57e44 in XrdCl::XRootDMsgHandler::HandleResponse (this=this@entry=0x60c350) at /home/simonm/git/xrootd/src/XrdCl/XrdClXRootDMsgHandler.cc:1120 #3 0x00007ffff7b5c08b in XrdCl::XRootDMsgHandler::Process (this=0x60c350, msg=0x7fffe4000950) at /home/simonm/git/xrootd/src/XrdCl/XrdClXRootDMsgHandler.cc:335 #4 0x00007ffff7b3dd3e in XrdCl::Stream::HandleIncMsgJob::Run (this=0x7fffe4000bf0, arg=<optimized out>) at /home/simonm/git/xrootd/src/./XrdCl/XrdClStream.hh:289 #5 0x00007ffff7b9f70f in XrdCl::JobManager::RunJobs (this=0x606fa0) at /home/simonm/git/xrootd/src/XrdCl/XrdClJobManager.cc:148 #6 0x00007ffff7b9f969 in RunRunnerThread (arg=<optimized out>) at /home/simonm/git/xrootd/src/XrdCl/XrdClJobManager.cc:33 #7 0x00007ffff72abdc5 in start_thread () from /lib64/libpthread.so.0 #8 0x00007ffff652973d in clone () from /lib64/libc.so.6 @bbockelm : any news on your side? Michal -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/499#issuecomment-293516075 ######################################################################## 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