 |
 |
Is there a core file? Can we get a backtrace with statement numbers? It's sort of opaque other than it crashed. Andy On Wed, 3 Oct 2018, Jan Iven wrote: > (again saw this - again when called by the `eos cp` frontend - with xrootd-libs-4.8.4-1.el6.x86_64). Same backtrace: > ``` > (gdb) bt > #0 0x00007f9bced2b4f5 in raise () from /lib64/libc.so.6 > #1 0x00007f9bced2ccd5 in abort () from /lib64/libc.so.6 > #2 0x00007f9bd06c4fce in XrdSys::IOEvents::PollE::Begin(XrdSysSemaphore*, int&, char const**) () from /usr/lib64/libXrdUtils.so.2 > #3 0x00007f9bd06c37cd in XrdSys::IOEvents::BootStrap::Start(void*) () from /usr/lib64/libXrdUtils.so.2 > #4 0x00007f9bd06c0a6f in XrdSysThread_Xeq () from /usr/lib64/libXrdUtils.so.2 > #5 0x00007f9bcf094aa1 in start_thread () from /lib64/libpthread.so.0 > #6 0x00007f9bcede1c4d in clone () from /lib64/libc.so.6 > (gdb) f 2 > #2 0x00007f9bd06c4fce in XrdSys::IOEvents::PollE::Begin(XrdSysSemaphore*, int&, char const**) () from /usr/lib64/libXrdUtils.so.2 > (gdb) print errno > $1 = 14 > ``` > > -- > You are receiving this because you were assigned. > Reply to this email directly or view it on GitHub: > https://github.com/xrootd/xrootd/issues/746#issuecomment-426538841 -- 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/746#issuecomment-426539557 ######################################################################## 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