[asterisk-bugs] [JIRA] (ASTERISK-20574) chan_motif crash

Tue Nov 6 08:49:21 CST 2012

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

Matt Jordan edited comment on ASTERISK-20574 at 11/6/12 8:48 AM:
-----------------------------------------------------------------

I've removed your backtrace from the comments and attached it as a separate file (ASTERISK-20574-backtrace.txt).  Please do not paste large blobs of anything (much less backtraces) in a comment - attach them as separate files.

Despite the fact that a chan_motif channel was being used at the time, this appears to be a crash occurring in MeetMe as it attempts to access the channel after it has been ref counted out.  This is more likely to be a general problem with MeetMe than a problem with the chan_motif channel driver.  Keep in mind that MeetMe in Asterisk 11 is an extended support module and development support for it comes primarily from the Asterisk community.

Finally, we are now repurposing this issue from a memory corruption crash in one version of Asterisk (a beta release) to a crash you experienced in a different part of the code, in a different scenario, with a different version.  Repurposing issues can become *very* confusing.  In the future, if you experience a problem and the scenario is not the same as what you initially reported, please open a new issue in Jira.  Thanks!

      was (Author: mjordan):
    I've removed your backtrace from the comments and attached it as a separate file (ASTERISK-20574-backtrace.txt).  Please do not paste large blobs of anything (much less backtraces) in a comment - attach them as separate files.

Despite the fact that a chan_motif channel was being used at the time, this appears to be a crash occurring in MeetMe as it attempts to access the channel after it has been ref counted out.  This is more likely to be a general problem with MeetMe than a problem with the chan_motif channel driver.  Keep in mind that MeetMe in Asterisk 11 is an extended support module and development support for it comes primarily from the Asterisk community.

> chan_motif crash
> ----------------
>
>                 Key: ASTERISK-20574
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20574
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_motif
>    Affects Versions: 11.0.0-beta2
>         Environment: Centos 5.8/x86
>            Reporter: Dmitry Melekhov
>            Assignee: Dmitry Melekhov
>            Severity: Minor
>         Attachments: ASTERISK-20574-backtrace.txt, motif.conf, xmpp.conf
>
>
> I'm trying to test calls between asterisk and psi with chan_motif with 11rc1 and just got crash:
> Program terminated with signal 11, Segmentation fault.
> #0  0x4fa00945 in memcpy () from /lib/libc.so.6
> (gdb) bt
> #0  0x4fa00945 in memcpy () from /lib/libc.so.6
> #1  0x4fb3e04d in ?? () from /lib/libz.so.1
> #2  0x4fb3f162 in ?? () from /lib/libz.so.1
> #3  0x4fb3e2f7 in deflate () from /lib/libz.so.1
> #4  0x4fcbd8aa in ?? () from /lib/libcrypto.so.6
> #5  0x4fcbd42e in COMP_compress_block () from /lib/libcrypto.so.6
> #6  0x4ffa148a in ssl3_do_compress () from /lib/libssl.so.6
> #7  0x4ffa15bd in ?? () from /lib/libssl.so.6
> #8  0x4ffa19d5 in ssl3_write_bytes () from /lib/libssl.so.6
> #9  0x4ff9efb1 in ssl3_write () from /lib/libssl.so.6
> #10 0x4ffb0879 in SSL_write () from /lib/libssl.so.6
> #11 0xb74d1eb9 in xmpp_client_send_raw_message (client=0xb7209f84, stanza=0x9c267e4) at res_xmpp.c:2409
> #12 ast_xmpp_client_send (client=0xb7209f84, stanza=0x9c267e4) at res_xmpp.c:2443
> #13 0xb64e0b4d in jingle_send_session_action (session=0x9c2a26c, action=0xb64e6c9f "session-initiate") at chan_motif.c:1318
> #14 0xb64e5f01 in jingle_send_session_initiate (ast=0x9c3b354, dest=0x9c0dec0 "jabber/dm at jabber.belkam.com", timeout=0) at chan_motif.c:1342
> not big deal just because I can't get sound between asterisk and psi yet, but anyway I guess there should be no crash... :-)
> #15 jingle_call (ast=0x9c3b354, dest=0x9c0dec0 "jabber/dm at jabber.belkam.com", timeout=0) at chan_motif.c:1682
> #16 0x080b8c28 in ast_call (chan=0x9c3b354, addr=0x9c0dec0 "jabber/dm at jabber.belkam.com", timeout=0) at channel.c:5959
> #17 0xb6d7662a in dial_exec_full (chan=0x9c0a544, data=<value optimized out>, peerflags=0xb4b1ae50, continue_exec=0x0) at app_dial.c:2594
> #18 0xb6d7a979 in dial_exec (chan=0x9c0a544, data=0xb4b1cf04 "Motif/jabber/dm at jabber.belkam.com,,r") at app_dial.c:3124
> #19 0x08165b70 in pbx_exec (c=0x9c0a544, app=0xb54954e0, data=0xb4b1cf04 "Motif/jabber/dm at jabber.belkam.com,,r") at pbx.c:1589
> #20 0x081769cd in pbx_extension_helper (c=0x9c0a544, con=0x0, context=0x9c0b0f8 "default", exten=0x9c0b148 "6006", priority=1, label=0x0, 
>     callerid=0x9bfea88 "6401", action=E_SPAWN, found=0xb4b1f328, combined_find_spawn=1) at pbx.c:4442
> #21 0x0817bdad in ast_spawn_extension (c=0x9c0a544, args=0x0) at pbx.c:5558
> #22 __ast_pbx_run (c=0x9c0a544, args=0x0) at pbx.c:6030
> #23 0x0817e870 in pbx_thread (data=0x9c0a544) at pbx.c:6360
> #24 0x081c220b in dummy_start (data=0x9c0d270) at utils.c:1030
> #25 0x4faf8852 in start_thread () from /lib/libpthread.so.0
> #26 0x4fa62a8e in clone () from /lib/libc.so.6

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira