[asterisk-bugs] [JIRA] (ASTERISK-17498) Asterisk Creates Core Dump on 'core stop gracefully'

[Corey Farrell (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-17498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Corey Farrell updated ASTERISK-17498:
-------------------------------------

    Assignee: Vladimir Mikhelson
      Status: Waiting for Feedback  (was: Open)

There have been many fixes to shutdown processes since this ticket was last touched.  Is this still an issue in the latest version of 11 or 13?  If so please attach new valgrind output and let us know which version.

Note Asterisk 1.8 is now receiving security fixes only.  See [Asterisk Versions|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions] for information on support for different versions.

> Asterisk Creates Core Dump on 'core stop gracefully'
> ----------------------------------------------------
>
>                 Key: ASTERISK-17498
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-17498
>             Project: Asterisk
>          Issue Type: Bug
>          Components: Core/General
>    Affects Versions: 1.8.3
>            Reporter: Vladimir Mikhelson
>            Assignee: Vladimir Mikhelson
>            Severity: Minor
>         Attachments: backtrace.2151.txt, backtrace.txt, mmlog, valgrind2.txt, valgrind.txt
>
>
> Sometimes when 'amportal restart' is executed in FreePBX Asterisk creates core dump.
> Amportal stops Asterisk by 'asterisk -rx "core stop gracefully"'
> Backtraces were created per https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace
> ****** ADDITIONAL INFORMATION ******
> Backtrace.txt and Backtrace2151.txt were composed from 2 dumps created today. The last one is different from the first one as in the last one Asterisk instance had res_timing_pthread.so preloaded in modules.conf in the course of troubleshooting issue ASTERISK-17396.



--
This message was sent by Atlassian JIRA
(v6.2#6252)