[asterisk-bugs] [JIRA] (ASTERISK-21305) Segfault when hanging up channels active in MeetMe with recording

Rusty Newton (JIRA) noreply at issues.asterisk.org
Mon Apr 1 19:42:01 CDT 2013


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

Rusty Newton updated ASTERISK-21305:
------------------------------------

    Attachment: trace-patched-ASTERISK21305.txt

Michael - Asterisk SVN-branch-1.8-r384410M with your patch failed compilation with 

{noformat}
app_meetme.c: In function ‘recordthread’:
app_meetme.c:5168:32: error: expected ‘;’ before ‘{’ token
{noformat}

Not being a C developer and not knowing Asterisk source I took a wild guess at what you were doing and put your expression into an if condition. Compilation was successful and I was still able to reproduce a crash using the script. 

Attaching trace-patched-ASTERISK21305.txt.  The trace looks quite different this time. Asterisk was compiled with DEBUG_THREADS, BETTER_BACKTRACES, DONT_OPTIMIZE
                
> Segfault when hanging up channels active in MeetMe with recording
> -----------------------------------------------------------------
>
>                 Key: ASTERISK-21305
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21305
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_meetme
>    Affects Versions: 1.8.15.1, 1.8.20.0, 11.2.1
>         Environment: Asterisk Now 2.0.0
> Asterisk Now 3.0.0
>            Reporter: Pedro Peña
>            Assignee: Rusty Newton
>         Attachments: asterisk-21305-meetme_rec_lchan_hangup.diff, backtrace1.txt, backtrace2.txt, backtrace3.txt, extensions_custom.conf, meetme_segfault.sh, trace-ASTERISK21305.txt, trace-patched-ASTERISK21305.txt
>
>
> The attached bash script (meetme_segfault.sh) causes a segfault in conjunction with the attached dialplan (extensions_custom.conf). The segfault happens in less than 10 seconds almost always.
> Note that if record disabled (comment line 3, uncomment line 4) the segfault not occurs.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



More information about the asterisk-bugs mailing list