You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@daffodil.apache.org by "Mike Beckerle (Jira)" <ji...@apache.org> on 2023/01/04 20:57:00 UTC

[jira] [Commented] (DAFFODIL-2733) trace output childIndex stack not correct

    [ https://issues.apache.org/jira/browse/DAFFODIL-2733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17654632#comment-17654632 ] 

Mike Beckerle commented on DAFFODIL-2733:
-----------------------------------------

This aspect of trace output is not relied upon anyway. 

> trace output childIndex stack not correct 
> ------------------------------------------
>
>                 Key: DAFFODIL-2733
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-2733
>             Project: Daffodil
>          Issue Type: Bug
>          Components: Back End, Debugger
>    Affects Versions: 3.3.0
>            Reporter: Mike Beckerle
>            Priority: Minor
>
> A trace output showed
> {code:java}
> childIndex: 178 -> 184{code}
> This makes no sense. Clearly this is being incremented, but the stack of it is not being properly maintained. As parsers unwind this should be going back down to the childIndex at that stack depth.
> There aren't 184 peer elements in the data I was testing with. There may be 184 element overall however. 
>  
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)