[asterisk-bugs] [JIRA] (ASTERISK-25534) Core dump on RTCP report/DNS lookup
Rusty Newton (JIRA)
noreply at issues.asterisk.org
Mon Nov 9 17:08:33 CST 2015
[ https://issues.asterisk.org/jira/browse/ASTERISK-25534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=228226#comment-228226 ]
Rusty Newton commented on ASTERISK-25534:
-----------------------------------------
Your backtrace appears to contain a memory corruption. We need one or both of the following items to continue investigation of the issue:
1. Valgrind output. See https://wiki.asterisk.org/wiki/display/AST/Valgrind for instructions on how to use Valgrind with Asterisk.
2. MALLOC_DEBUG output. See https://wiki.asterisk.org/wiki/display/AST/MALLOC_DEBUG+Compiler+Flag for instructions on how to use the MALLOC_DEBUG option.
Note that MALLOC_DEBUG and Valgrind are mutually exclusive options. Valgrind output is preferable, but will be more system resource intensive and may be difficult to get on a production system. In such a case, you may have better luck getting the necessary output from MALLOC_DEBUG.
> Core dump on RTCP report/DNS lookup
> -----------------------------------
>
> Key: ASTERISK-25534
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-25534
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: General
> Affects Versions: 13.6.0
> Reporter: Morten Tryfoss
> Assignee: Unassigned
> Severity: Critical
> Attachments: backtrace.txt
>
>
> Asterisk crashed. There might have been a slight drop on the connectivity against the DNS server at the point, but the host it tried lookup on (it's own hostname) is added to /etc/hosts too.
> No info in the logs at the time of the crash. It happened in the middle of the night with just about one simultaneous call on the system.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list