[asterisk-bugs] [JIRA] (ASTERISK-25370) res_corosync segfaults at startup (probably the same issue as in ASTERISK-24343)

[Rusty Newton (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-25370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rusty Newton updated ASTERISK-25370:
------------------------------------

    Assignee: mdu113  (was: Unassigned)
      Status: Waiting for Feedback  (was: Triage)

[~mdu113] can you reproduce this with a default installation of Asterisk and sample config files?

That is, can you reproduce this issue without touching anything on a fresh installation?

It'll help to narrow it down to something in your configuration/build or something in the environment (if that is possible - it could be a combination).

> res_corosync segfaults at startup (probably the same issue as in ASTERISK-24343)
> --------------------------------------------------------------------------------
>
>                 Key: ASTERISK-25370
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25370
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_corosync
>    Affects Versions: 11.19.0
>         Environment: linux 64bit
> kernel 3.10.17
> distro slackware64 14.1
> corosync 2.3.5
>            Reporter: mdu113
>            Assignee: mdu113
>         Attachments: backtrace.txt, valgrind.txt
>
>
> Asterisk crashes at startup when trying to load res_corosync.so. The content of res_corosync.conf doesn't matter. As long as file exists (even empty one) asterisk segfaults. 
> The issue seems identical to the one described in ASTERISK-24343, but since that issue was closed due to no feedback, I'm opening a new one.
> Backtrace is attached.
> I've also tested it in asterisk 13.5.0 and got the same result - asterisk segfaults. The backtrace is taken from 11.19.0 though as that one I'm currently using.
> Thanks



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