 |
 |
This came up again - and this time I'm sure I didn't delete the XrdCl::File (one thread's stack trace shows as waiting on the results of the kXR_open). Here's a process which segfaulted while XrdCl::File::Close is called from the main thread and the worker pool is in UnPackReadVResponse: http://glidemon.web.cern.ch/glidemon/show.php?log=http://vocms20.cern.ch/mon/cms980/140427_011655_vocms20:bbockelm_crab_xrootd_test_14/job_out.25.0.txt Here's a process that segfaulted in OnOpen like first reported above: http://glidemon.web.cern.ch/glidemon/show.php?log=http://vocms20.cern.ch/mon/cms980/140427_011655_vocms20:bbockelm_crab_xrootd_test_14/job_out.1113.0.txt (but this time we had the extra protection to make sure we're not deleting the file). The two new cases are with 4.0.0-rc1; the older example was with 3.3.3-rc1. Looking through all three examples given, they all segfaulted while trying to recover inside the XrdCl. I found six segfaults that look like this; all six happened while running recovery. --- Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/107#issuecomment-41498591 ######################################################################## 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