[asterisk-bugs] [Asterisk 0015109]: Abort by memory allocator, possibly in moh_files_generator
Asterisk Bug Tracker
noreply at bugs.digium.com
Fri Jul 31 06:50:06 CDT 2009
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=15109
======================================================================
Reported By: jvandal
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 15109
Category: Resources/res_musiconhold
Reproducibility: random
Severity: block
Priority: normal
Status: acknowledged
Target Version: 1.4.27
Asterisk Version: 1.4.24
Regression: No
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2009-05-14 10:49 CDT
Last Modified: 2009-07-31 06:50 CDT
======================================================================
Summary: Abort by memory allocator, possibly in
moh_files_generator
Description:
I have a server running with Asterisk 1.4.24.1 where it randomly segfault
for "unknown" reason.
I'm not sure if this is related to moh_files_generator function or with
filestream_descructor.
Let me know what needed in order to fix this crash, if GDB traces aren't
enough.
Asterisk is compiled with DONT_OPTIMIZE and others flag needed for "gdb".
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0014958 Segfault Asterisk 1.4.24.1
related to 0015123 out of bounds crash and core dump
related to 0015506 Asterisk 1.4.26rc5 (revision 202945 ) d...
parent of 0015396 app_queue segfault in revision 202945
has duplicate 0015195 double free or corruption (!prev) in mo...
======================================================================
----------------------------------------------------------------------
(0108455) davidw (reporter) - 2009-07-31 06:50
https://issues.asterisk.org/view.php?id=15109#c108455
----------------------------------------------------------------------
The original fault, here, was NOT a segfault. It's signal 3, which is the
result of the library code software deliberately declaring an error,
whereas a segfault is signal 11, which is detected by the hardware, when
the code accesses an address (in a way) that the address translation
hardware thinks it should not.
Issue History
Date Modified Username Field Change
======================================================================
2009-07-31 06:50 davidw Note Added: 0108455
======================================================================
More information about the asterisk-bugs
mailing list