Project

Profile

Help

Bug #19

closed

Tracing of FLWOR expressions

Added by Anonymous almost 13 years ago. Updated over 12 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Diagnostics
Sprint/Milestone:
-
Start date:
Due date:
% Done:

100%

Estimated time:
Legacy ID:
sf-3469431
Applies to branch:
Fix Committed on Branch:
Fixed in Maintenance Release:
Platforms:

Description

SourceForge user: mhkay

The new 9.4 implementation of FLWOR expressions does not allow fine-grained tracing/monitoring at the clause level, which is problem for tools that implement a debugger. A patch (rather extensive) to fix this deficiency is being placed in Subversion. The patch introduces a new kind of FLWOR clause, the TraceClause, and a new method on the CodeInjector allowing TraceClauses to be injectied into a FLWOR pipeline; the TraceClause notifies the TraceListener of each tuple at run time, whether the pipeline is run in pull or push mode.

Actions #1

Updated by Anonymous almost 13 years ago

SourceForge user: mhkay

A further patch has been added in Subversion revision 667 which makes namespace information available to a TraceListener when invoked at the level of a clause in a FLWOR expression. This is needed by one of the debuggers that operates with Saxon.

Actions #2

Updated by Anonymous almost 13 years ago

SourceForge user: mhkay

Fixed in 9.4.0.2

Actions #3

Updated by Anonymous almost 13 years ago

SourceForge user: mhkay

The second patch, to provide namespace information to the trace listener, is incomplete in the version issued with 9.4.0.2. A new patch is therefore being raised which makes further changes to the TraceClause and ClauseInfo.

Actions #4

Updated by Michael Kay over 12 years ago

  • Status changed from New to Resolved
Actions #5

Updated by Michael Kay over 12 years ago

  • Status changed from Resolved to Closed
  • % Done changed from 0 to 100

Please register to edit this issue

Also available in: Atom PDF