[asterisk-bugs] [JIRA] Commented: (ASTERISK-19532) Asterisk crashed after connecting with jabber server in component mode

[Matt Jordan (JIRA)]

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

Matt Jordan commented on ASTERISK-19532:
----------------------------------------

I went ahead and committed Byron's patch, with some small modifications to resolve ASTERISK-19557 as well.  If this doesn't resolve this issue, please let me know and I'll reopen it.  Thanks!

> Asterisk crashed after connecting with jabber server in component mode
> ----------------------------------------------------------------------
>
>                 Key: ASTERISK-19532
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-19532
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_jabber
>    Affects Versions: 1.8.10.0, 1.8.11.0
>         Environment: Debian squeeze, asterisk 1.8.10.0
>            Reporter: Karsten Wemheuer
>         Attachments: fix-jabber, xmpp_no_crash_with_ejabberd.patch
>
>
> I connect asterisk with a xmpp server in component mode (jabberd2). Up to asterisk 1.8.8.2 all was working fine. In version 1.8.10.0 asterisk crashes on startup after handshaking with jabber server.
> I do a backtrace and some debugging, and I found out, that the crash happens in function aji_dinfo_handler() at the end. In line 2203:
> {code}
> ASTOBJ_UNREF(buddy, ast_aji_buddy_destroy);
> {code}
> the macro is called with buddy=NULL. In 1.8.8.2 there was no call to this macro.
> The attached simple patch solves the issue, but I am not sure, that this is the right way. The statement mentioned above was added in many places in res_jabber.c between version 1.8.8.2 and 1.8.10.0. Should all get fixed this way?

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira