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

[Steve Davies (JIRA)]

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

Steve Davies edited comment on ASTERISK-22079 at 1/30/14 12:46 PM:
-------------------------------------------------------------------

Matt,

Perhaps I am mistaken about how the scheduler fires. I thought it was:

{{task timer expires}}
{{monospaced}}res = run task()
{{monospaced}}if ( res <= 0 ) {
{{monospaced}}  delete task
{{monospaced}}} else {
{{monospaced}}  reschedule same task in res milliseconds
{{monospaced}}}


So the event cannot be deleted until AFTER the task has run because it needs the result of the run to know whether to delete it or resched it.


                
      was (Author: one47):
    Matt,

Perhaps I am mistaken about how the scheduler fires. I thought it was:

{{monospaced}}task timer expires
{{monospaced}}res = run task()
{{monospaced}}if ( res <= 0 ) {
{{monospaced}}  delete task
{{monospaced}}} else {
{{monospaced}}  reschedule same task in res milliseconds
{{monospaced}}}


So the event cannot be deleted until AFTER the task has run because it needs the result of the run to know whether to delete it or resched it.


                  
> 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