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

Matt Jordan (JIRA) noreply at issues.asterisk.org
Thu Jan 30 12:37:05 CST 2014


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

Matt Jordan commented on ASTERISK-22079:
----------------------------------------

I think our discussion on asterisk-dev is showing that we can't shoot it down :-( (Obligatory reference: [http://lists.digium.com/pipermail/asterisk-dev/2014-January/064885.html])

Even with your trace above, I think I'm still confused how the scheduler delete is occurring (that is, how it is un'refing the pvt). If the scheduler callback has fired, that should have removed the item from the scheduler, meaning the scheduler delete will never succeed. Some extra debug may help illuminate how it is getting into that spot.

Or else I'm just missing something :-)

                
> 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-gdb-output.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