[asterisk-bugs] [Asterisk 0017615]: asterisk chrased while playing MP3 [WARNING[21708]: mp3/interface.c:215 decodeMP3: Junk at xxxxx]
Asterisk Bug Tracker
noreply at bugs.digium.com
Fri Jul 9 13:20:02 CDT 2010
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=17615
======================================================================
Reported By: gkservice
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 17615
Category: Addons/General
Reproducibility: always
Severity: crash
Priority: normal
Status: new
Asterisk Version: 1.4.31
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-09 08:05 CDT
Last Modified: 2010-07-09 13:20 CDT
======================================================================
Summary: asterisk chrased while playing MP3 [WARNING[21708]:
mp3/interface.c:215 decodeMP3: Junk at xxxxx]
Description:
Asterisk crashed while playing a MP3 File
>>>>>>>>>>>>>>>>>>>>>>
[Jul 9 14:30:38] WARNING[21708]: mp3/interface.c:215 decodeMP3: Junk at
the beginning of frame 49443303
lenny*CLI> *** glibc detected *** /usr/sbin/asterisk: malloc(): memory
corruption: 0x00002aaab8129010 ***
[Jul 9 14:30:38] WARNING[21708]: mp3/interface.c:215 decodeMP3: Junk at
the beginning of frame 00000000
>>>>>>>>>>>>>>>>>>>>>>
======================================================================
----------------------------------------------------------------------
(0124405) lmadsen (administrator) - 2010-07-09 13:20
https://issues.asterisk.org/view.php?id=17615#c124405
----------------------------------------------------------------------
You'll need to attach a backtrace and valgrind output. See the following
notes:
----
It looks like it could be a memory corruption issue.
Please see the doc/valgrind.txt file in your Asterisk source directory for
more information about how to produce debugging information. Thanks!
----
Thank you for your bug report. In order to move your issue forward, we
require a backtrace from the core file produced after the crash. Please see
the doc/backtrace.txt file in your Asterisk source directory.
Also, be sure you have DONT_OPTIMIZE enabled in menuselect within the
Compiler Flags section, then:
make install
after enabling, reproduce the crash, and then execute the instructions in
doc/backtrace.txt.
When complete, attach that file to this issue report. Thanks!
Issue History
Date Modified Username Field Change
======================================================================
2010-07-09 13:20 lmadsen Note Added: 0124405
======================================================================
More information about the asterisk-bugs
mailing list