Hi Tomasso,
Too bad you are leaving tonight (weren't you supposed to talk tomorrow?).
Yes, this is what I need. You can find out which thread gt the SEGV by
doing "info threads" the one with the asterisk in the running thread that
failed. That's the one we need the traceback for (so "thread <n>" followed
by where).
Andy
On Wed, 5 Nov 2014, Tommaso Boccali wrote:
> ciao, so here it is:
>
> Core was generated by `/usr/bin/xrootd -l /var/log/xrootd/xrootd.log -c /etc/xrootd/xrootd-redir-cms-f'.
> Program terminated with signal 11, Segmentation fault.
> #0 0x0000000000417743 in XrdXrootdMonFile::GetSlot (slotSZ=8)
> at /usr/src/debug/xrootd/xrootd/src/XrdXrootd/XrdXrootdMonFile.cc:439
> 439 repTOD->tBeg = htonl(static_cast<int>(time(0)));
>
> and the 'where' says
>
> #0 0x0000000000417743 in XrdXrootdMonFile::GetSlot (slotSZ=8)
> at /usr/src/debug/xrootd/xrootd/src/XrdXrootd/XrdXrootdMonFile.cc:439
> #1 0x0000000000417cb6 in XrdXrootdMonFile::Disc (usrID=0)
> at /usr/src/debug/xrootd/xrootd/src/XrdXrootd/XrdXrootdMonFile.cc:200
> #2 0x000000000041c71a in XrdXrootdProtocol::Recycle (this=0x7f0890000990, lp=
> 0x7f0894000a88, csec=3, reason=<value optimized out>)
>
> is this what you need? not sure how to find 'the thread that got the SEGV'.
> I am leaving early tonight ... tomorrow ~ after 11 am ?
>
> tom
>
>
>
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/xrootd/xrootd/issues/155#issuecomment-61843993
—
Reply to this email directly or view it on GitHub.
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