[asterisk-bugs] [JIRA] Commented: (ASTERISK-16975) Segmentation Fault: #0 0x080d5dcb in ast_readaudio_callback (s=0xb2e1fa98) at file.c:762

[Jeff Hoppe (JIRA)]

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

Jeff Hoppe commented on ASTERISK-16975:
---------------------------------------

Kristijan, the next time I got this error I was going to apply the patch.  I never got the error before I upgraded to Asterisk 10.  After running asterisk 10 for 8 months I just got the same or similar error.  See attachments for the back trace.

Can you create a patch that will work in Asterisk 10  (10.6 is my current version, I don't see any fixes to this issue in the 10.8 change log).

> Segmentation Fault:  #0  0x080d5dcb in ast_readaudio_callback (s=0xb2e1fa98) at file.c:762
> ------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-16975
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-16975
>             Project: Asterisk
>          Issue Type: Bug
>          Components: Channels/General
>            Reporter: Jeff Hoppe
>            Severity: Critical
>         Attachments: backtrace032411.txt, backtrace10032012.txt, backtrace1117A.txt, backtrace_2011-06-09.txt, gbb_2.txt, Thread5986.txt, workaround_ASTERISK-16975.patch
>
>
> Program terminated with signal 11, Segmentation fault.
> #0  0x080d5dcb in ast_readaudio_callback (s=0xb2e1fa98) at file.c:762
> 762			if (s->owner->timingfd > -1) {
> (gdb) bt
> #0  0x080d5dcb in ast_readaudio_callback (s=0xb2e1fa98) at file.c:762
> #1  0x080d5fdf in ast_fsread_audio (data=0xb2e1fa98) at file.c:789
> #2  0x08098ca6 in __ast_read (chan=0xb46ed038, dropaudio=0) at channel.c:2784
> #3  0x0809a852 in ast_read (chan=0xb46ed038) at channel.c:3181
> #4  0x080958de in ast_safe_sleep_conditional (chan=0xb46ed038, ms=68, cond=0xa0a7ee <agent_cont_sleep>, 
>     data=0x99f1da8) at channel.c:1385
> ASTERISK-1  0x00a0feb5 in login_exec (chan=0xb46ed038, data=0xb5794e78) at chan_agent.c:2236
> ASTERISK-2  0x080fbcd4 in pbx_exec (c=0xb46ed038, app=0x99f0f68, data=0xb5794e78) at pbx.c:1352
> ASTERISK-3  0x08103a03 in pbx_extension_helper (c=0xb46ed038, con=0x0, context=0xb46ed2ac "station", 
>     exten=0xb46ed2fc "7270", priority=4, label=0x0, callerid=0xb46281f0 "s3s033", action=E_SPAWN, 
>     found=0xb57972ec, combined_find_spawn=1) at pbx.c:3715
> ASTERISK-4  0x08104f97 in ast_spawn_extension (c=0xb46ed038, context=0xb46ed2ac "station", exten=0xb46ed2fc "7270", 
>     priority=4, callerid=0xb46281f0 "s3s033", found=0xb57972ec, combined_find_spawn=1) at pbx.c:4186
> ASTERISK-5  0x08105638 in __ast_pbx_run (c=0xb46ed038, args=0x0) at pbx.c:4280
> ASTERISK-6 0x08106a91 in pbx_thread (data=0xb46ed038) at pbx.c:4567
> ASTERISK-7 0x08159dca in dummy_start (data=0xb4c271e8) at utils.c:968
> ASTERISK-8 0x0067073b in start_thread () from /lib/libpthread.so.0
> ASTERISK-9 0x005eecfe in clone () from /lib/libc.so.6
> ****** ADDITIONAL INFORMATION ******
> This is actually version 1.6.2.13   I did not see any changes regarding this in the 1.6.2.14 change log.  I will upgrade to this newer version but I put this here because it was identified as being fixed in 1.6.2.10 in a related issue (0017686)

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