You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@daffodil.apache.org by "Michael Beckerle (JIRA)" <ji...@apache.org> on 2019/07/26 19:54:00 UTC
[jira] [Commented] (DAFFODIL-2189) Unparse with trace on causes
Abort
[ https://issues.apache.org/jira/browse/DAFFODIL-2189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16894083#comment-16894083 ]
Michael Beckerle commented on DAFFODIL-2189:
--------------------------------------------
We need some unit tests that run with trace on, so as to insure that the debugger/trace works for a round-trip test. Otherwise it is too easy to break something that only fails under tracing/debug, but not notice.
> Unparse with trace on causes Abort
> ----------------------------------
>
> Key: DAFFODIL-2189
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2189
> Project: Daffodil
> Issue Type: Bug
> Components: Debugger
> Affects Versions: 2.4.0
> Reporter: Michael Beckerle
> Priority: Major
> Fix For: 2.5.0
>
>
> I tried to trace a round-trip test. The parse side works. The unparse does not.
> {code:java}
> org.apache.daffodil.exceptions.Abort: Invariant broken: org.apache.daffodil.util.Maybe.WithNulls.isDefined[org.apache.daffodil.infoset.DINode](UState.this.currentInfosetNode)
> org.apache.daffodil.exceptions.Assert$.abort(Assert.scala:129)
> org.apache.daffodil.processors.unparsers.UState.infoset(UState.scala:124)
> org.apache.daffodil.debugger.InteractiveDebugger$DebugCommandBase$Info$InfoInfoset$.act(InteractiveDebugger.scala:1506)
> org.apache.daffodil.debugger.InteractiveDebugger$DebugCommandBase$Info$.$anonfun$act$20(InteractiveDebugger.scala:1209)
> at org.apache.daffodil.exceptions.Assert$.abort(Assert.scala:129)
> at org.apache.daffodil.processors.unparsers.UState.infoset(UState.scala:124)
> at ....
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)