Thanks for reporting the problem you have found. Just to let you know we are currently investigating it.

On 16/11/12 01:40, John Barstow wrote:
After some investigation, I've added the following two lines to the
Saxon.Api.XsltCompiler constructor:

            if (config.isCompileWithTracing())
                info.setCodeInjector(new TimingCodeInjector());

After adding these lines and re-compiling, I am now able to correctly
profile XSLT transforms. The -TP flag modifies a default CompilerInfo
instance, but the .NET code always creates a new instance, thus losing
the code injector. My solution seemed to be the most surgical fix, but
it might be more correct to clone the default instance. I'll let
someone with greater knowledge of the Java internals make that call.

Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
saxon-help mailing list archived at 

Kind regards,

O'Neil Delpratt
Software Developer, Saxonica Limited
Tel: +44 118 946 5894
Saxonica Community Site: Saxonica Bug tracking System: