It does indeed look like a static deinitialization order fiasco and the reason for why it isn't is subtle. You will see it if you read the whole bug report carefully. The reason it does not segfault earlier is that the memory chunk that was holding the text segment of the XrdCls ELF object has not been tainted nor unmmapped and XrdCl's code has this stuff in a couple of places: https://github.com/xrootd/xrootd/blob/master/src/XrdCl/XrdClFile.cc#L63

You should try @jknedlik 's snipped for yourself. AFAIK pretty much all the data analysis IO traffic goes through ROOT IO, so you will likely see this kind of stuff again.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

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