[asterisk-bugs] [JIRA] (ASTERISK-22688) astobj2.c: bad magic number - core dump

Gareth Blades (JIRA) noreply at issues.asterisk.org
Fri Oct 25 18:40:03 CDT 2013


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

Gareth Blades commented on ASTERISK-22688:
------------------------------------------

I don't have access to the server at the moment but it was compiled from source with no changes made to the compiler settings so it will be whatever 'make menuselect' has at default.
                
> astobj2.c: bad magic number - core dump
> ---------------------------------------
>
>                 Key: ASTERISK-22688
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22688
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/PBX
>    Affects Versions: 11.2.0
>         Environment: Centos 6.4 64bit
> Asterisk 11.2-cert2
> glibc-2.12-1.107.el6_4.2.x86_64
>            Reporter: Gareth Blades
>            Assignee: Matt Jordan
>         Attachments: core backtrace.txt
>
>
> Server has been up for 50 days and regularly handles 60 concurrent calls (we have other busier servers). Today we had a core dump. 
> In the asterisk logs :-
> [Oct 14 15:55:53] ERROR[1650] astobj2.c: bad magic number for 0x7fb67452dad8. Object is likely destroyed.
> Kernel messages :-
> Oct 14 15:55:53 gw3 kernel: asterisk[1650]: segfault at 18 ip 00000034f1f3b8ff sp 00007fb679908088 error 4 in libc-2.12.so[34f1e00000+18a000]
> Oct 14 15:56:00 gw3 abrt[7599]: Saved core dump of pid 1630 (/usr/sbin/asterisk) to /var/spool/abrt/ccpp-2013-10-14-15:55:53-1630 (171835392 bytes)
> I see that there is a newer glibc 2.12-1.107.el6_4.4 available.
> Please could you advise if its an asterisk issue or definitely a fault with glibc. I will upload the core dump shortly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



More information about the asterisk-bugs mailing list