[
https://issues.apache.org/jira/browse/MESOS-6254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Rukletsov updated MESOS-6254:
---------------------------------------
Description:
[Some child
hooks|https://github.com/apache/mesos/blob/ec4c81a12559030791334359e7e1e2b6565cce01/3rdparty/libprocess/src/subprocess.cpp#L67]
create an {{Error}} instance, which is strictly speaking not async signal safe.
We should either refactor {{Error}} to be no-throw or avoid using it in child
hooks.
was:
[Some child
hooks|https://github.com/apache/mesos/blob/ec4c81a12559030791334359e7e1e2b6565cce01/3rdparty/libprocess/src/subprocess.cpp#L67]
create an {{Error}} instance, which is strictly speaking no async signal safe.
We should either refactor {{Error}} to be no-throw or avoid using it in child
hooks.
> Child hooks are not async signal safe.
> --------------------------------------
>
> Key: MESOS-6254
> URL: https://issues.apache.org/jira/browse/MESOS-6254
> Project: Mesos
> Issue Type: Bug
> Affects Versions: 1.0.0, 1.0.1
> Reporter: Alexander Rukletsov
> Labels: mesosphere
>
> [Some child
> hooks|https://github.com/apache/mesos/blob/ec4c81a12559030791334359e7e1e2b6565cce01/3rdparty/libprocess/src/subprocess.cpp#L67]
> create an {{Error}} instance, which is strictly speaking not async signal
> safe.
> We should either refactor {{Error}} to be no-throw or avoid using it in child
> hooks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
