[asterisk-bugs] [Asterisk 0015109]: Abort by memory allocator, possibly in moh_files_generator
Asterisk Bug Tracker
noreply at bugs.digium.com
Fri May 15 10:44:22 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: crash
Priority: normal
Status: feedback
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-05-15 10:44 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
======================================================================
----------------------------------------------------------------------
(0104835) lmadsen (administrator) - 2009-05-15 10:44
https://issues.asterisk.org/view.php?id=15109#c104835
----------------------------------------------------------------------
Well, basically valgrind will most likely keep Asterisk from crashing, so
what you'll want to do is see if you can easily reproduce outside of
valgrind, then reproduce the same test inside valgrind. Once you've
executed your test, then you can attach the valgrind files here.
The reason for doing it this way is that you probably won't get a crash
from Asterisk while inside of valgrind.
Issue History
Date Modified Username Field Change
======================================================================
2009-05-15 10:44 lmadsen Note Added: 0104835
======================================================================
More information about the asterisk-bugs
mailing list