[jira] [Commented] (DAFFODIL-2348) Debugger breaks with prefixed lengths

["Mike Beckerle (Jira)" <ji...@apache.org>]

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

Mike Beckerle commented on DAFFODIL-2348:
-----------------------------------------

We also need to think of a testing strategy for the debugger so that this sort of thing gets covered. 
E.g., perhaps there's a mode which runs every one of our TDML tests with debugger on? 

> Debugger breaks with prefixed lengths
> -------------------------------------
>
>                 Key: DAFFODIL-2348
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-2348
>             Project: Daffodil
>          Issue Type: Bug
>          Components: Debugger
>    Affects Versions: 2.6.0
>            Reporter: Steve Lawrence
>            Priority: Major
>
> When using the debugger and displaying the infoset (e.g. info infoset), if the current element is a prefixed length element Daffodil will abort with an exception about "No parent element for element (prefixLength)". This is because the debugger tries to find the root element:
> {code:scala}
> infoset = infoset.toRootDoc.getRootElement().asInstanceOf[DIElement]
> {code}
> But that fails when the element is a prefixed length element. Need special logic somewhere to handle these detached elements.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)