[asterisk-bugs] [JIRA] (ASTERISK-23835) crash: Segfault in manager during lookup of action "Login" in action_find

[Matt Jordan (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-23835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=219173#comment-219173 ] 

Matt Jordan commented on ASTERISK-23835:
----------------------------------------

Looking at your most recent backtrace:

{noformat}
Core was generated by `/usr/sbin/asterisk -f -vvvg -c'.
Program terminated with signal 11, Segmentation fault.
#0  0xb76e2652 in ?? ()
#0  0xb76e2652 in ?? ()
No symbol table info available.
#1  0x0815406f in named_acl_find_realtime (
    name=0xc80fdd0 "\r\ncret: info47sDz\r\n\r\nk\r\nSecret: info47sDz\r\n\r\nrisk\r\nSecret: info47sDz\r\n\r\n: info47sDz\r\n\r\n") at named_acl.c:271
        cfg = 0x0
        item = 0xadd86aef ""
        systemname = 0x12 <Address 0x12 out of bounds>
        built_ha = 0xadd86a88
        acl = 0xb76e0ec8
        __PRETTY_FUNCTION__ = "named_acl_find_realtime"
#2  0x0815776c in pbx_exec (c=0xa96494b4, app=0x0, data=0x2 <Address 0x2 out of bounds>) at pbx.c:1579
        res = 1401750001
        u = 0x538d01f1
        saved_c_appl = 0x1 <Address 0x1 out of bounds>
        saved_c_data = 0x0
        __PRETTY_FUNCTION__ = "pbx_exec"
#3  0x081b28bd in ast_translator_deactivate (t=0xa96494b4) at translate.c:1184
        __PRETTY_FUNCTION__ = "ast_translator_deactivate"
#4  0x081bfcc5 in xmldoc_parse_variablelist (node=0xa9cef8c0, tabs=0xadd87b70 "p{ح@ۿ\260p{ح\001", buffer=0xadd87b70) at xmldoc.c:1538
        tmp = 0xadd87394
        varname = 0xb77b0ff4 "|-\024"
        vartabs = 0x0
        ret = -1221613690
        __PRETTY_FUNCTION__ = "xmldoc_parse_variablelist"
#5  0xb72fa955 in ?? ()
No symbol table info available.
#6  0xb773a1de in ?? ()
No symbol table info available.
{noformat}

# This crash is in a completely different location. 
# The backtrace still has symbols optimized out of it.

The biggest problem is point #1. You seem to have a variety of problems going on here, and I'm not sure it is related at all to manager.

Based on the sporadic nature of your crashes, you may have a memory corruption of some sort occurring. Try profiling Asterisk under valgrind - see [https://wiki.asterisk.org/wiki/display/AST/Valgrind] for information on running Asterisk under valgrind.

> crash: Segfault in manager during lookup of action "Login" in action_find
> -------------------------------------------------------------------------
>
>                 Key: ASTERISK-23835
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-23835
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/ManagerInterface
>    Affects Versions: 11.2.2
>         Environment: Debian 6.0.7 virtualized on Proxmox 3.1 (KVM) 
> Memory 1Gb 
> CPU 2.27 GHz (1 socket)
>            Reporter: Matteo
>            Assignee: Matt Jordan
>            Severity: Critical
>         Attachments: backtrace_better.txt, backtrace.txt
>
>
> Segfault of asterisk
> An external process is connected with the manager interface to monitor the peer status and execute click to dial function.
> last week after more than 60 days the asterisk process goes into a segfault.
> from the backtrace seems link to action_find in manager.c



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