 |
 |
No, I agree, it doesn't ... it looks like a memory overwrite or double delete. But the thing might have gone through a different failure mode (abrupt destruction of cache file object) later on (or before) because of other bugs. I tried breaking off client connection to force it but got no pie. I thought Edgar spoke to you about the issues (seen while testing http proxy for ligo) and that that led you to start looking into http problems. We only saw the above crash once (with unpatched version) and there was no core (or we lost it during rebuild of kubernetes container). -- 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/808#issuecomment-418632513 ######################################################################## 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