[asterisk-bugs] [Asterisk 0017686]: Asterisk crashing in ast_readaudio_callback at file.c:762
Asterisk Bug Tracker
noreply at bugs.digium.com
Mon Jul 26 04:48:48 CDT 2010
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=17686
======================================================================
Reported By: jhoppebugs
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 17686
Category: General
Reproducibility: random
Severity: crash
Priority: normal
Status: new
Asterisk Version: 1.6.2.9
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2010-07-22 12:43 CDT
Last Modified: 2010-07-26 04:48 CDT
======================================================================
Summary: Asterisk crashing in ast_readaudio_callback at
file.c:762
Description:
Program terminated with signal 11, Segmentation fault.
https://issues.asterisk.org/view.php?id=0 0x080d54db in ast_readaudio_callback
(s=0xb358d5e8) at file.c:762
762 if (s->owner->timingfd > -1) {
https://issues.asterisk.org/view.php?id=0 0x080d54db in ast_readaudio_callback
(s=0xb358d5e8) at file.c:762
whennext = 160
__PRETTY_FUNCTION__ = "ast_readaudio_callback"
https://issues.asterisk.org/view.php?id=1 0x080d56ef in ast_fsread_audio
(data=0xb358d5e8) at file.c:789
fs = 0xb358d5e8
res = FSREAD_SUCCESS_SCHED
https://issues.asterisk.org/view.php?id=2 0x08098a76 in __ast_read
(chan=0xb59b72f8, dropaudio=0) at
channel.c:2784
func = 0x80d56d8 <ast_fsread_audio>
data = 0xb358d5e8
res = AST_TIMING_EVENT_EXPIRED
f = 0x0
blah = -1255758064
prestate = 6
count = 0
cause = 0
__PRETTY_FUNCTION__ = "__ast_read"
https://issues.asterisk.org/view.php?id=3 0x0809a539 in ast_read
(chan=0xb59b72f8) at channel.c:3163
No locals.
======================================================================
----------------------------------------------------------------------
(0125006) davidw (reporter) - 2010-07-26 04:48
https://issues.asterisk.org/view.php?id=17686#c125006
----------------------------------------------------------------------
If this is the problem we had, it will be almost impossible to reproduce it
(without having worked out what the underlying problem is). It took several
months for the first one to occur, and we have only had one. I may have a
debug log available, but unlike the original reporter, I don't have a
proper backtrace. I didn't report it at the time because I knew we didn't
meet the reporting requirements.
There is nothing unusual in our debug log, it just shows a call being
offered to the agent and then the restart.
Incidentally, the boiler plate is incorrect; you do fix non-reproducible
problems if a detailed mechanism is supplied, and especially if a patch is
provided.
We are taking steps to ensure we get a better backtrace next time, but it
is quite likely we will not see this problem again. Although I suspect
there is a memory overwrite involved, we are not going to be able to run
valgrind on a customer system for months on end, and probably not at all,
both for perforamnce and configuration management reasons.
Unfortunately Asterisk is highly dependent on locking and omissions in
that area can produce faults that are extremely timing critical.
Issue History
Date Modified Username Field Change
======================================================================
2010-07-26 04:48 davidw Note Added: 0125006
======================================================================
More information about the asterisk-bugs
mailing list