[asterisk-bugs] [JIRA] (ASTERISK-27625) channels: CHECK_BLOCKING is ineffective

[Corey Farrell (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-27625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Corey Farrell updated ASTERISK-27625:
-------------------------------------

    Attachment: backtrace-rest_api-danger-dangerous.txt
                backtrace-channels-pjsip-transfers-attended_transfer-nominal-caller_local_blonde.txt
                backtrace-channels-pjsip-dtmf_info_fallback.txt

When an assert was added to the error path it caused testsuite failures.  These are the backtraces collected.  The rest_api and dtmf_info_fallback are from 13, caller_local_blonde is from 15.

> channels: CHECK_BLOCKING is ineffective
> ---------------------------------------
>
>                 Key: ASTERISK-27625
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27625
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/Channels
>    Affects Versions: 13.19.0, GIT, 15.2.0
>            Reporter: Corey Farrell
>            Assignee: Corey Farrell
>            Severity: Minor
>         Attachments: backtrace-channels-pjsip-dtmf_info_fallback.txt, backtrace-channels-pjsip-transfers-attended_transfer-nominal-caller_local_blonde.txt, backtrace-rest_api-danger-dangerous.txt
>
>
> {{CHECK_BLOCKING}} is used to set blocking flag/pthread/function is unset, but does not return success or error.  In all cases the caller of {{CHECK_BLOCKING}} ends up clearing the blocking flag (which it might not have even been set by the current thread).



--
This message was sent by Atlassian JIRA
(v6.2#6252)