You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@daffodil.apache.org by "Steve Lawrence (Jira)" <ji...@apache.org> on 2026/10/06 19:46:00 UTC

[jira] [Commented] (DAFFODIL-3104) output reports unparser as unavailable in trace/debug mode

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

Steve Lawrence commented on DAFFODIL-3104:
------------------------------------------

Possible duplicate of DAFFODIL-2709, depending on if this is fixed with a new "info processor" debugger command or something else.

> output reports unparser as unavailable in trace/debug mode
> ----------------------------------------------------------
>
>                 Key: DAFFODIL-3104
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-3104
>             Project: Daffodil
>          Issue Type: Bug
>          Components: Debugger
>    Affects Versions: 4.2.0
>            Reporter: Olabusayo Kilo
>            Priority: Minor
>
> When tracing or debugging while unparsing, we get  "parser: unavailable" and get no output for the unparser case. what we need is a new {{info processor}} command or something that will inspect the state and output either the parser or unparser depending on the state. We should maybe even just deprecate {{info parser/unparser}} and have them call into {{{}info processor{}}}, users shouldn't have to worry about it we're parsing or unparsing.



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