[asterisk-bugs] [JIRA] (ASTERISK-24343) res_corosync segfaults in dispatch_thread_handler

[Rusty Newton (JIRA)]

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

Rusty Newton commented on ASTERISK-24343:
-----------------------------------------

Suspended due to lack of activity. Please request a bug marshal in #asterisk-bugs on the IRC network irc.freenode.net to reopen the issue should you have the additional information requested.  Further information can be found at http://www.asterisk.org/developers/bug-guidelines



> res_corosync segfaults in dispatch_thread_handler
> -------------------------------------------------
>
>                 Key: ASTERISK-24343
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24343
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_corosync
>    Affects Versions: 13.0.0-beta2
>         Environment: linux 64bit
> kernel 3.16.2
> asterisk r423616
>            Reporter: Marcello Ceschia
>         Attachments: backtrace.txt
>
>
> I have to set noload => res_corosync.so in modules.conf
> When loading res_corosync from cli:
> {code}
> *CLI> module load res_corosync.so
>   == Parsing '/etc/asterisk/res_corosync.conf': Found
>  Loaded res_corosync.so => (Corosync)
> Loaded res_corosync.so
> *CLI> Speicherzugriffsfehler (Speicherabzug geschrieben)
> {code}
> Backtrace see backtrace.txt



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