[asterisk-bugs] [JIRA] (ASTERISK-22079) Segfault: INTERNAL_OBJ (user_data=0x6374652f) at astobj2.c:120
Matt Jordan (JIRA)
noreply at issues.asterisk.org
Fri Feb 28 12:38:05 CST 2014
[ https://issues.asterisk.org/jira/browse/ASTERISK-22079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=215784#comment-215784 ]
Matt Jordan commented on ASTERISK-22079:
----------------------------------------
Awesome. Thanks for the reproduction, analysis, and ref_debug log.
I agree with the workaround, although it's ugly :-) Really, the scheduler should be "smart enough" to handle those details for the caller. That would necessitate some full blown changes to the scheduler API, which - barring no other solution - we'd probably try to avoid in Asterisk 1.8 and 11.
> 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
More information about the asterisk-bugs
mailing list