qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PROTON-1493) c-proactor make pn_proactor_interrupt async-signal-safe
Date Wed, 31 May 2017 14:50:04 GMT

    [ https://issues.apache.org/jira/browse/PROTON-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031269#comment-16031269

ASF subversion and git services commented on PROTON-1493:

Commit 5f8738f573c3e9c39608714453b2425e3a105ec7 in qpid-proton's branch refs/heads/master
from [~aconway]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=5f8738f ]

PROTON-1493: c-proactor make pn_proactor_interrupt async-signal-safe

pn_proactor_interrupt() will  often be used from signal handlers so must be
async-signal-safe. Updated the documentation and modified the implementations
of pn_proactor_interrupt() to use only async-signal-safe calls, no locks.

> c-proactor make pn_proactor_interrupt async-signal-safe
> -------------------------------------------------------
>                 Key: PROTON-1493
>                 URL: https://issues.apache.org/jira/browse/PROTON-1493
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: proton-c
>    Affects Versions: 0.17.0
>            Reporter: Alan Conway
>            Assignee: Alan Conway
>             Fix For: 0.18.0
> pn_proactor_interrupt() should be async signal safe, as it will often be used in signal
handlers. The current implementations use mutexes and counters which are not.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

View raw message