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/06/19 23:24:00 UTC

[jira] [Commented] (DAFFODIL-1931) Debug/trace - prints spurious error message about ".."

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

Michael Beckerle commented on DAFFODIL-1931:
--------------------------------------------

Increasing priority to blocker. This message is completely confusing to any new users, and makes the trace output very hard to use.

Fixing the trace output generally is important, but getting rid of this very confusing message that one must know to disregard, is really important.

> Debug/trace - prints spurious error message about ".."
> ------------------------------------------------------
>
>                 Key: DAFFODIL-1931
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-1931
>             Project: Daffodil
>          Issue Type: Bug
>          Components: Debugger
>    Affects Versions: 2.1.0
>            Reporter: Michael Beckerle
>            Priority: Blocker
>             Fix For: 2.4.0
>
>
> Whenever I use debug/trace now, every step I see:
> {code}
> Debugger error: expression evaluation failed: Schema Definition Error: Relative path '..' past root element.
> Schema context: element reference ex:e1 Location line 1 in file:/tmp/anon5232752542024144234.dfdl.xsd
> {code}
> This is due to the debugger/trace own internal use of ".." in a path evaluation in order to display the infoset I believe. Any step where there is no current infoset element gets this error.
> At one time there was code to specifically catch this and suppress it, but code changes must have modified the thrown exception in a way that now bypasses the logic that suppressed this. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)