[
https://issues.apache.org/jira/browse/GEODE-2713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15941030#comment-15941030
]
ASF GitHub Bot commented on GEODE-2713:
---------------------------------------
GitHub user PivotalSarge opened a pull request:
https://github.com/apache/geode-native/pull/74
GEODE-2713: Wrap result collector lock in shared_ptr.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/PivotalSarge/geode-native feature/GEODE-2713
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/geode-native/pull/74.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #74
----
commit 422b9dbe1e59621019c971b111322a9b49b431d7
Author: Sarge <mdo...@pivotal.io>
Date: 2017-03-24T18:06:29Z
GEODE-2713: Wrap result collector lock in shared_ptr.
----
> Function execution can lead to passing the address of a stack variable
> ----------------------------------------------------------------------
>
> Key: GEODE-2713
> URL: https://issues.apache.org/jira/browse/GEODE-2713
> Project: Geode
> Issue Type: Bug
> Components: native client
> Reporter: Michael Dodge
>
> In ThinClientRegion::executeFunctionSH(), the address of a stack variable
> (the result collector lock) is passed to the workers. If an exception occurs
> with any of the workers, the function will return, causing the stack variable
> to be destructed. Since the workers have the raw address, it is now a
> dangling pointer situation.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
