 |
 |
Hi Brian, We have lots of core files and they die in various places. Usually in malloc, though. So, it's definitely a heap corruption. None of them indicate anything other that either null pointer in a free block, a 0x26 (usually) in a unique pointer, and the like. The log files show no particular errors related to the crashes. I think the first step is to determine why that line was commented out. Accoding to reports if the buffer size is not reset, curl will likely corrupt memory. Do you recll what commit commented that line out? That may help us find a "good" release which would be a smoking gun. Andy On Sun, 10 Oct 2021, Brian P Bockelman wrote: > Hi Andy! > > Do you have any specific reports to share on this (logfiles, traceback, core files, etc). > > Don't recall why that line was commented out. > > B > > -- > You are receiving this because you authored the thread. > Reply to this email directly or view it on GitHub: > https://github.com/xrootd/xrootd/issues/1531#issuecomment-939575018 -- 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/1531#issuecomment-939706368 ######################################################################## 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