[
https://issues.apache.org/jira/browse/DAFFODIL-2385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Thompson closed DAFFODIL-2385.
-----------------------------------
Per Josh this issue was resolved in commit
f1603a0da8c9610f7ade79250315a2b5db333db2 for Jira ticket DAFFODIL-2429, which
was verified and closed. After re-reviewing the commit Josh found that he had
added tests that verified the issue identified in this ticket. Closing this
ticket as verified with DAFFODIL-2429.
> newVariableInstance has issues with suspensions during unparse
> --------------------------------------------------------------
>
> Key: DAFFODIL-2385
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2385
> Project: Daffodil
> Issue Type: Bug
> Components: Back End
> Affects Versions: 2.7.0
> Reporter: Josh Adams
> Assignee: Josh Adams
> Priority: Major
> Fix For: 3.1.0
>
>
> While doing some work for a customer schema I ran into an issue where I was
> using newVariableInstance and setting a variable based on the value of
> another element. This other element has an outputValueCalc that performs
> dfdl:valueLength() on a section of data.
> I believe what is happening is that the newVariableInstance starts its scope
> and tries to set its variable but suspends until the dfdl:valueLength() call
> can be resolved. In the meantime there is another call to NVI and setVariable
> on the same variable which results in the variable being set twice and
> causing an error. Removing the outputValueCalc resolves this issue, which
> leads me to believe that the suspension is resulting in the variable stack
> getting clobbered.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
