Asterisk 1.6.2.22 backtrace

Home » Asterisk Users » Asterisk 1.6.2.22 backtrace
Asterisk Users 7 Comments

Hello,

what does it mean when you read in the backtrace file :

Reading symbols from /lib64/libgcc_s.so.1…(no debugging symbols
found)…done.
Loaded symbols for /lib64/libgcc_s.so.1
Core was generated by `/usr/sbin/asterisk -f -vvvg -c’.
Program terminated with signal 6, Aborted.
#0 0x00000035f2230285 in raise () from /lib64/libc.so.6

Terminated with signal 6, what is that ?

7 thoughts on - Asterisk 1.6.2.22 backtrace

  • Hello,

    is this an answer or is the most of your answer missing ?

    I don’t understand what you mean and I still don’t understand what
    happened with Asterisk.

  • That would be his answer. If you type kill -l, you’ll get a listing of signals:

    kill -l

    1) SIGHUP 2) SIGINT 3) SIGQUIT 4) SIGILL 5) SIGTRAP
    6) SIGABRT

    6 would be signal abort.

    Doug

  • To give a more verbose answer, the line in the backtrace that says no
    debugging symbols found answers the rest of your question: It’s not
    possible to tell where the signal comes from, because asterisk was built
    without debugging symbols. This is not a proper backtrace in that it
    doesn’t trace back to anything. So we can’t say from this what caused the
    problem.

    Regards,

    Stephen J Alexander
    MPBX, LLC
    http://mpbx.com
    832-713-6729

  • I have selected ” don’t optimize ” in the menuselect for better
    information in the trace and now you tell me that it’s still useless ?

    (off course the trace created with bt full is more verbose, but I cant’
    post all that)

  • No debugging symbols are avaialble for libgcc_s . Libgcc is an external
    library, which is part of gcc and includes code generated by it. Its
    debug information would probably be included in a package such as
    libgcc-debuginfo . Try installing it.

    That said, debug information for external libraries is often not that
    important for Asterisk crashes.

  • (As mentioned in a separate post, this is not related to the missing
    debug symbols from the external library libgcc_s)

    Have you reproduced the crash with that rebuilt Asterisk? If you rebuild
    (and later install) Asterisk with different build options, the original
    core dump becomes useless, as the code has changed (and may reside in
    different addresses).