[asterisk-bugs] [JIRA] (ASTERISK-22079) Segfault: INTERNAL_OBJ (user_data=0x6374652f) at astobj2.c:120

[Matteo (JIRA)]

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

Matteo commented on ASTERISK-22079:
-----------------------------------

Few second before the segfault into messsage file there are these lines:

[2014-02-18 10:35:42] ERROR[1721] astobj2.c: bad magic number for 0x9f152a90. Object is likely destroyed.
[2014-02-18 10:35:42] WARNING[1721] chan_sip.c: Unable to get seqno from ''
[2014-02-18 10:35:42] ERROR[1721] astobj2.c: bad magic number for 0x9f152a90. Object is likely destroyed.
[2014-02-18 10:35:47] WARNING[1721] chan_sip.c: Retransmission timeout reached on transmission 3cf57a34c47c-14zp42q5mgep for seqno 2 (Critical Response) -- See https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions
Packet timed out after 31999ms with no response
[2014-02-18 10:36:33] NOTICE[4380] features.c: pickup SIP/4002-00012afb attempt by SIP/4003-00012b03
[2014-02-18 10:36:42] ERROR[1721] astobj2.c: bad magic number for 0x9f152a90. Object is likely destroyed.
[2014-02-18 10:36:42] WARNING[1721] chan_sip.c: Unable to get seqno from ''
[2014-02-18 10:36:42] ERROR[1721] astobj2.c: bad magic number for 0x9f152a90. Object is likely destroyed.
                
> Segfault: INTERNAL_OBJ (user_data=0x6374652f) at astobj2.c:120
> --------------------------------------------------------------
>
>                 Key: ASTERISK-22079
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22079
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/General
>    Affects Versions: 1.8.23.0
>         Environment: Linux CentOS 5.9 32-bit as a VM on XenServer 5.6 SP2
>            Reporter: Jamuel Starkey
>            Assignee: Jamuel Starkey
>         Attachments: asterisk-22079-backtrace-leif.txt, asterisk-22079-gdb-output.txt, backtrace_asterisk.11.2.certified.txt
>
>
> We discovered this segfault while running a debug build 1.8.23.0-rc1.  Although not entirely clear it's likely that this issue was triggered during an asterisk "reload" operation that would have been sent over AMI.
> Attaching the output of gdb (bt, bt full, thread apply all bt) as per the Debug guidelines found on the wiki.

--
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