[asterisk-bugs] [Asterisk 0010997]: Asterisk 1.4.13 segfaults at least once daily
noreply at bugs.digium.com
noreply at bugs.digium.com
Wed Oct 17 17:57:21 CDT 2007
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=10997
======================================================================
Reported By: aragon
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 10997
Category: Core-General
Reproducibility: N/A
Severity: crash
Priority: normal
Status: new
Asterisk Version: 1.4.13
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 10-16-2007 10:52 CDT
Last Modified: 10-17-2007 17:57 CDT
======================================================================
Summary: Asterisk 1.4.13 segfaults at least once daily
Description:
System segfaults at least once daily
Started segfaulting after upgrade from 1.2.24 to 1.4.11
Tried many upgrades in increments
1.4.11
1.4.12
1.4.12 SVN
1.4.12.1
1.4.13
Problem still exists in 1.4.13
I dont know what steps are needed to reproduce.
======================================================================
----------------------------------------------------------------------
aragon - 10-17-07 17:57
----------------------------------------------------------------------
New coredump this afternoon and I think this time DONT_OPTIMIZE was
compiled correctly but not with MALLOC_DEBUG enabled.
The resulting backtrace does not look anything like my first backtrace but
bears a striking resemblance to http://bugs.digium.com/view.php?id=10841
Tonight I plan to recompile with MALLOC_DEBUG enabled and wait for the
next coredump.
If this anything in common with 10841 I whould be able to generate a
segfault by sending some faxes to the main number.
I hope I am dealing with one bug and not two separate issues.
I guess the only way to know for sure is to remove the one problem and see
if the site keeps crashing.
Here is todays backtrace
It was confirmed that at at 16h37:17, extension 721 received a faxtone
721 is my reception phone so I presume the inbound fax was an unsolicited
fax to the main number.
The back trace timestamp is 16:37:46
http://bugs.digium.com/view.php?id=0 0x006bb7a2 in _dl_sysinfo_int80 () from
/lib/ld-linux.so.2
(gdb) set pagination off
(gdb) bt full
http://bugs.digium.com/view.php?id=0 0x006bb7a2 in _dl_sysinfo_int80 () from
/lib/ld-linux.so.2
No symbol table info available.
http://bugs.digium.com/view.php?id=1 0x006fc7a5 in raise () from
/lib/tls/libc.so.6
No symbol table info available.
http://bugs.digium.com/view.php?id=2 0x006fe209 in abort () from
/lib/tls/libc.so.6
No symbol table info available.
http://bugs.digium.com/view.php?id=3 0x00730a1a in __libc_message () from
/lib/tls/libc.so.6
No symbol table info available.
http://bugs.digium.com/view.php?id=4 0x007372bf in _int_free () from
/lib/tls/libc.so.6
No symbol table info available.
http://bugs.digium.com/view.php?id=5 0x0073763a in free () from
/lib/tls/libc.so.6
No symbol table info available.
http://bugs.digium.com/view.php?id=6 0x080b9e69 in frame_cache_cleanup ()
No symbol table info available.
http://bugs.digium.com/view.php?id=7 0x00885258 in __nptl_deallocate_tsd ()
from /lib/tls/libpthread.so.0
No symbol table info available.
http://bugs.digium.com/view.php?id=8 0x008853da in start_thread () from
/lib/tls/libpthread.so.0
No symbol table info available.
http://bugs.digium.com/view.php?id=9 0x0079dc3e in clone () from
/lib/tls/libc.so.6
No symbol table info available.
Issue History
Date Modified Username Field Change
======================================================================
10-17-07 17:57 aragon Note Added: 0072208
======================================================================
More information about the asterisk-bugs
mailing list