[
https://issues.apache.org/jira/browse/DAFFODIL-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17741786#comment-17741786
]
Olabusayo Kilo commented on DAFFODIL-2694:
------------------------------------------
I was able to get trace working, but I'm struggling to get the TDMLProcessor to
drop into an interactive debugger. I'm doing something like the below when the
runner is created, but it just runs through without dropping into the debugger
even when I provide a file with the debugger command "help display". Am I
missing something?
{code:java}
val db = conf.debug() match {
case Some(f) => new CLIDebuggerRunner(new File(f), STDIN, STDOUT)
case None => new CLIDebuggerRunner(STDIN, STDOUT)
}
val id = new InteractiveDebugger(db, ExpressionCompilers)
tdmlRunnerInit.setDebugger(id){code}
> CLI -t trace option doesn't work for daffodil test commands in TDML
> -------------------------------------------------------------------
>
> Key: DAFFODIL-2694
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2694
> Project: Daffodil
> Issue Type: New Feature
> Components: TDML Runner
> Affects Versions: 3.3.0
> Reporter: Mike Beckerle
> Assignee: Olabusayo Kilo
> Priority: Major
>
> This command does not cause tracing:
> {code:java}
> daffodil -t test -iii src/test/resources/owl/myTests.tdml testName
> {code}
> It is important and very convenient when using CLI and TDML to be able to
> trace a single test.
> The general -t (for trace) option should apply to running TDML as well as
> parse/unparse.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
