You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@trafficserver.apache.org by "Brian Geffon (JIRA)" <ji...@apache.org> on 2013/02/25 23:00:14 UTC

[jira] [Commented] (TS-935) Should EVENT_INTERNAL really be the same as TS_EVENT_TIMEOUT

    [ https://issues.apache.org/jira/browse/TS-935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13586347#comment-13586347 ] 

Brian Geffon commented on TS-935:
---------------------------------

It's a bug, TSContCall with TS_EVENT_IMMEDIATE will cause a segfault because the event count goes negative. I'll look at it tomorrow when I'm up in portland.
                
> Should EVENT_INTERNAL really be the same as TS_EVENT_TIMEOUT
> ------------------------------------------------------------
>
>                 Key: TS-935
>                 URL: https://issues.apache.org/jira/browse/TS-935
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: TS API
>    Affects Versions: 3.0.1
>            Reporter: Brian Geffon
>            Assignee: Brian Geffon
>             Fix For: 3.3.3
>
>
> When trying to use TSContCall with event = TS_EVENT_TIMEOUT I stumbled upon the fact that the API will decrement the event count for EVENT_INTERNAL or EVENT_IMMEDIATE (see INKContInternal::handle_event_count), but shouldn't we be able to do a TSContCall with TS_EVENT_IMMEDIAITE or TS_EVENT_TIMEOUT because as of now doing so would cause m_event_count to become -1 or shouldn't these defined values be something different? 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira