[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=220424#comment-220424 ] 

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

Your issue is not related to a deadlock. The only thing {{DEBUG_THREADS}} does is to enable debugging of deadlock situations - it has nothing to do with your issue, and you should not be running Asterisk with {{DEBUG_THREADS}}.

Based on the backtrace you've provided, I would suspect you have something that valgrind would point out. I'd like to say that we could help diagnose and fix this problem without that, but it's unlikely to happen.

If you are unable or unwilling to run Asterisk under valgrind, then this issue will be closed out.

> 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: Matteo
>            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)