[asterisk-bugs] [JIRA] (ASTERISK-23835) Segfault manager.c

[Matt Jordan (JIRA)]

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

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

# The backtrace has a number of optimized symbols stripped out of it. That will make determining why the lookup for the AMI action caused a seg fault difficult. Please attach a backtrace generated from an instance of Asterisk with {{DONT_OPTIMIZE}} and {{BETTER_BACKTRACES}} enabled.
# If you have the core file still, and symbols are present, open it up in gdb ({{gdb -se asterisk -c core}} - and print the values of the following:
** {{frame 0}}
** {{print *actions}}
** {{print *act}}
** {{print *act->action}}


> Segfault manager.c
> ------------------
>
>                 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
>            Severity: Critical
>         Attachments: 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)