[ https://issues.apache.org/jira/browse/GEODE-2713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15955702#comment-15955702 ]
ASF GitHub Bot commented on GEODE-2713: --------------------------------------- Github user PivotalSarge commented on the issue: https://github.com/apache/geode-native/pull/74 To quote Montgomery Scott, "I did what I could, Captain!" > On 4 Apr, 2017, at 11:40, Ernie Burghardt <notificati...@github.com> wrote: > > @PivotalSarge <https://github.com/PivotalSarge> need to clean up this PR, should not have all of the docs commits included, TIA > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub <https://github.com/apache/geode-native/pull/74#issuecomment-291593880>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ATlz4qbKjC__AlGa5bSDX0mzozBlrF1mks5rso6pgaJpZM4Mosqr>. > > 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)