[asterisk-bugs] [JIRA] Commented: (ASTERISK-20474) Segfault Asterisk 1.8.15 on vmware

[Matt Jordan (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-20474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=198046#comment-198046 ] 

Matt Jordan commented on ASTERISK-20474:
----------------------------------------

While I appreciate the numerous backtraces, its clear that this is occurring due to a memory corruption (seg faults while allocating memory).  The backtraces will not provide any additional information, since the seg faults are occurring in multiple locations.

If you are unable to run this under valgrind, you may want to at least try compiling Asterisk with MALLOC_DEBUG and seeing if it reports any memory fence violations.  That would be the best chance - outside of valgrind - of actually finding this problem.

Without that information, I don't think there's going to be anything anyone can do to help you.

> Segfault Asterisk 1.8.15 on vmware
> ----------------------------------
>
>                 Key: ASTERISK-20474
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20474
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 1.8.15.0
>         Environment: IBM System X 3500
> Four-core Intel ® Xeon E5620 2.40 GHz with 12 MB of cache per processor socket standard with 12 MB of cache per processor socket
> 12 GB RAM 
> 450 HD SATA - RAID1
> OS Guest: VMware ESXi 4.1 Server - IBM Build Official
> -----
> Performs just one VM:
> VM: CentOS 6.3 
> Storage: 50 GB
> Mem: 12 GB RAM
> Linux centralip-dev 2.6.32-279.5.2.el6.x86_64 #1 SMP Fri Aug 24 01:07:11 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
> Asterisk: 1.8.15.0
> ---
>            Reporter: Alex Cremonezi
>            Assignee: Alex Cremonezi
>            Severity: Critical
>         Attachments: backtrace-2012-09-10.txt, backtrace-2012-09-18.txt, backtrace-2012-09-24.txt, backtrace-2012-10-04.txt
>
>
> Every two weeks a segfault happens in my asterisk. I can not reproduce this segfault because I do not know the exact reason, but always occurs in the middle of the afternoon, about every two weeks.
> About 500 extensions. About 40 simultaneous connections.
> Segfault occurred 3 times this month (September, 2012):
> September 10, 2012 at 15h16
> September 18, 2012 at 15h58
> September 24, 2012 at 15h12
> The three backtraces are attached.
> When I performs the command " grep segfault /var/log/messages* ", results:
> ../messages:Sep 24 15:12:10 localhost kernel: asterisk[7285]: segfault at 7f950000001a ip 00007f9625e80599 sp 00007f95d8106af0 error 4 in libc-2.12.so[7f9625e08000+186000]
> ../messages-20120902:Aug 31 15:37:55 localhost kernel: asterisk[32114]: segfault at 7f6600000010 ip 00007f67258cc4de sp 00007f668b7bc560 error 6 in libc-2.12.so[7f6725854000+186000]
> ../messages-20120916:Sep 10 15:16:53 localhost kernel: asterisk[6384]: segfault at 7f5d0000001a ip 00007f5e57eb4599 sp 00007f5e09682bc0 error 4 in libc-2.12.so[7f5e57e3c000+186000]
> ../messages-20120923:Sep 18 15:58:11 localhost kernel: asterisk[8093]: segfault at 12 ip 00007f4a84176489 sp 00007f4a31587b70 error 6 in libc-2.12.so[7f4a840fe000+186000]
> Thanks!

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira