Summary:ASTERISK-16407: Crashes due to memory issues in Manager.c [ _ast_malloc ] [Possibly related to 0017234]
Reporter:Jeff Hoppe (jhoppebugs)Labels:
Date Opened:2010-07-22 12:48:06Date Closed:2011-06-07 14:00:57
Versions:Frequency of
Environment:Attachments:( 0) gdb0720.txt
Description:#0  0x00a96410 in __kernel_vsyscall ()
No symbol table info available.
#1  0x00545df0 in raise () from /lib/libc.so.6
No symbol table info available.
#2  0x00547701 in abort () from /lib/libc.so.6
No symbol table info available.
#3  0x0057e28b in __libc_message () from /lib/libc.so.6
No symbol table info available.
#4  0x00587559 in _int_malloc () from /lib/libc.so.6
No symbol table info available.
ASTERISK-1  0x00588d87 in malloc () from /lib/libc.so.6
No symbol table info available.
ASTERISK-2  0x081582b9 in _ast_malloc (len=314, file=0x81a2ff4 "manager.c", lineno=3300, func=0x81a51aa "append_event")
   at /usr/src/asterisk-
       p = 0x0
       __PRETTY_FUNCTION__ = "_ast_malloc"
ASTERISK-3  0x080f5852 in append_event (
   str=0x8f6651c "Event: RTCPReceived\r\nPrivilege: reporting,all\r\nFrom:\r\nPT: 200(Sender Report)\r\nReceptionReports: 1\r\nSenderSSRC: 0\r\nFractionLost: 0\r\nPacketsLost: 0\r\nHighestSequence: 45901\r\nSequenceNumb"..., category=512) at manager.c:3300
       tmp = 0xb58de66c
       __PRETTY_FUNCTION__ = "append_event"
       seq = 1871367
ASTERISK-4  0x080f5b14 in __manager_event (category=512, event=0x81acb69 "RTCPReceived", file=0x81ac214 "rtp.c",
   line=1410, func=0x81ac7fb "ast_rtcp_read",
   fmt=0x81aca90 "From: %s:%d\r\nPT: %d(%s)\r\nReceptionReports: %d\r\nSenderSSRC: %u\r\nFractionLost: %ld\r\nPacketsLost: %d\r\nHighestSequence: %ld\r\nSequenceNumberCycles: %ld\r\nIAJitter: %u\r\nLastSR: %lu.%010lu\r\nDLSR: %4.4f(sec)\r\n"...) at manager.c:3369
       session = 0x67750ccf
       hook = 0x91914c0
       auth = 0xb58de680
       cat_str = 0xb58de68c "reporting,all"
       ap = 0xb58de758 "\300\024\031\tw\301"
       now = {tv_sec = 2, tv_usec = -1248991424}
       buf = 0x8f66510
       seq = 0
Comments:By: Tilghman Lesher (tilghman) 2010-07-22 20:15:11

Your backtrace appears to contain memory corruption and we require valgrind output in order to move this issue forward.

Please see the doc/valgrind.txt file in your Asterisk source directory for more information about how to produce debugging information. Thanks!

By: Paul Belanger (pabelanger) 2010-08-04 11:55:36

Suspended due to lack of activity. Please request a bug marshal in #asterisk-bugs on the IRC network irc.freenode.net to reopen the issue should you have the additional information requested.

Further information can be found at http://www.asterisk.org/developers/bug-guidelines