internal error evaluating template rule regression error

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

internal error evaluating template rule regression error

David Rudel
Hello,
I have a stylesheet that runs as expected on Saxon 9.6.0.7 but throws
an "internal error evaluating template rule" error in Saxon 9.7.0.4.

I noticed the bug reported here https://saxonica.plan.io/issues/2770
and wonder whether this sort of thing is expected in cases where a
template is plain match template (rather than having both a name and a
match pattern). My template is a simple matching template.

If not, are there other known issues that could cause this?

I'm willing to make a repro, but would rather not replicate other
work. The stylesheet I'm using will take some work to simplify.

--

"A false conclusion, once arrived at and widely accepted is not
dislodged easily, and the less it is understood, the more tenaciously
it is held." - Cantor's Law of Preservation of Ignorance.

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. http://sdm.link/zohodev2dev
_______________________________________________
saxon-help mailing list archived at http://saxon.markmail.org/
[hidden email]
https://lists.sourceforge.net/lists/listinfo/saxon-help 
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: internal error evaluating template rule regression error

Michael Kay
The message ""internal error evaluating template rule" is very generic; if you have a stack trace, it's the next exception on the stack trace (the "cause" of the internal error) that tells us what's really happening. So we can't really judge whether this is a known error without seeing that further detail.

Michael Kay
Saxonica

> On 13 Aug 2016, at 21:15, David Rudel <[hidden email]> wrote:
>
> Hello,
> I have a stylesheet that runs as expected on Saxon 9.6.0.7 but throws
> an "internal error evaluating template rule" error in Saxon 9.7.0.4.
>
> I noticed the bug reported here https://saxonica.plan.io/issues/2770
> and wonder whether this sort of thing is expected in cases where a
> template is plain match template (rather than having both a name and a
> match pattern). My template is a simple matching template.
>
> If not, are there other known issues that could cause this?
>
> I'm willing to make a repro, but would rather not replicate other
> work. The stylesheet I'm using will take some work to simplify.
>
> --
>
> "A false conclusion, once arrived at and widely accepted is not
> dislodged easily, and the less it is understood, the more tenaciously
> it is held." - Cantor's Law of Preservation of Ignorance.
>
> ------------------------------------------------------------------------------
> What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
> patterns at an interface-level. Reveals which users, apps, and protocols are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity
> planning reports. http://sdm.link/zohodev2dev
> _______________________________________________
> saxon-help mailing list archived at http://saxon.markmail.org/
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/saxon-help 



------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. http://sdm.link/zohodev2dev
_______________________________________________
saxon-help mailing list archived at http://saxon.markmail.org/
[hidden email]
https://lists.sourceforge.net/lists/listinfo/saxon-help 
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: internal error evaluating template rule regression error

David Rudel
I'm using oXygen, is there a configuration file option that will show
the stack trace when an error occurs?

Unfortunately, I cannot run 9.7.0.4 in debugger mode, as it is an
external tool at this point.

I'll try to make a small repro and send it in.


On Sun, Aug 14, 2016 at 6:11 AM, Michael Kay <[hidden email]> wrote:

> The message ""internal error evaluating template rule" is very generic; if you have a stack trace, it's the next exception on the stack trace (the "cause" of the internal error) that tells us what's really happening. So we can't really judge whether this is a known error without seeing that further detail.
>
> Michael Kay
> Saxonica
>
>> On 13 Aug 2016, at 21:15, David Rudel <[hidden email]> wrote:
>>
>> Hello,
>> I have a stylesheet that runs as expected on Saxon 9.6.0.7 but throws
>> an "internal error evaluating template rule" error in Saxon 9.7.0.4.
>>
>> I noticed the bug reported here https://saxonica.plan.io/issues/2770
>> and wonder whether this sort of thing is expected in cases where a
>> template is plain match template (rather than having both a name and a
>> match pattern). My template is a simple matching template.
>>
>> If not, are there other known issues that could cause this?
>>
>> I'm willing to make a repro, but would rather not replicate other
>> work. The stylesheet I'm using will take some work to simplify.
>>
>> --
>>
>> "A false conclusion, once arrived at and widely accepted is not
>> dislodged easily, and the less it is understood, the more tenaciously
>> it is held." - Cantor's Law of Preservation of Ignorance.
>>
>> ------------------------------------------------------------------------------
>> What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
>> patterns at an interface-level. Reveals which users, apps, and protocols are
>> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
>> J-Flow, sFlow and other flows. Make informed decisions using capacity
>> planning reports. http://sdm.link/zohodev2dev
>> _______________________________________________
>> saxon-help mailing list archived at http://saxon.markmail.org/
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/saxon-help
>
>
>
> ------------------------------------------------------------------------------
> What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
> patterns at an interface-level. Reveals which users, apps, and protocols are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity
> planning reports. http://sdm.link/zohodev2dev
> _______________________________________________
> saxon-help mailing list archived at http://saxon.markmail.org/
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/saxon-help



--

"A false conclusion, once arrived at and widely accepted is not
dislodged easily, and the less it is understood, the more tenaciously
it is held." - Cantor's Law of Preservation of Ignorance.

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. http://sdm.link/zohodev2dev
_______________________________________________
saxon-help mailing list archived at http://saxon.markmail.org/
[hidden email]
https://lists.sourceforge.net/lists/listinfo/saxon-help 
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: internal error evaluating template rule regression error

David Rudel
In reply to this post by Michael Kay
The following stylesheet throws the error with 9.7.0.4 but not
9.6.0.7. I've included some modifications that do not throw an error.

<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="3.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:math="http://exslt.org/math"
xmlns:map="http://www.w3.org/2005/xpath-functions/map"
>
<xsl:template match="/">
<xsl:variable name="error-causing-map" as="map(xs:string,xs:double)">
<xsl:map>
<xsl:for-each select="'a'">
<xsl:map-entry key="'a'" select="xs:double(2)"/>
</xsl:for-each>
</xsl:map>
</xsl:variable>
<xsl:variable name="no-error-map" as="map(*)">
<xsl:map>
<xsl:map-entry key="'a'" select="2"/>
</xsl:map>
</xsl:variable>
<!--This throws an error with 9.7.0.4 but not 9.6.0.7-->
<xsl:value-of select="math:power($error-causing-map('a'),2)"/>
<!-- None of the following throws an error:
<xsl:value-of select="math:power($no-error-map('a'),2)"/>
<xsl:value-of select="math:power(+$error-causing-map('a'),2)"/>-->
</xsl:template>
</xsl:stylesheet>

On Sun, Aug 14, 2016 at 6:11 AM, Michael Kay <[hidden email]> wrote:

> The message ""internal error evaluating template rule" is very generic; if you have a stack trace, it's the next exception on the stack trace (the "cause" of the internal error) that tells us what's really happening. So we can't really judge whether this is a known error without seeing that further detail.
>
> Michael Kay
> Saxonica
>
>> On 13 Aug 2016, at 21:15, David Rudel <[hidden email]> wrote:
>>
>> Hello,
>> I have a stylesheet that runs as expected on Saxon 9.6.0.7 but throws
>> an "internal error evaluating template rule" error in Saxon 9.7.0.4.
>>
>> I noticed the bug reported here https://saxonica.plan.io/issues/2770
>> and wonder whether this sort of thing is expected in cases where a
>> template is plain match template (rather than having both a name and a
>> match pattern). My template is a simple matching template.
>>
>> If not, are there other known issues that could cause this?
>>
>> I'm willing to make a repro, but would rather not replicate other
>> work. The stylesheet I'm using will take some work to simplify.
>>
>> --
>>
>> "A false conclusion, once arrived at and widely accepted is not
>> dislodged easily, and the less it is understood, the more tenaciously
>> it is held." - Cantor's Law of Preservation of Ignorance.
>>
>> ------------------------------------------------------------------------------
>> What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
>> patterns at an interface-level. Reveals which users, apps, and protocols are
>> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
>> J-Flow, sFlow and other flows. Make informed decisions using capacity
>> planning reports. http://sdm.link/zohodev2dev
>> _______________________________________________
>> saxon-help mailing list archived at http://saxon.markmail.org/
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/saxon-help
>
>
>
> ------------------------------------------------------------------------------
> What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
> patterns at an interface-level. Reveals which users, apps, and protocols are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity
> planning reports. http://sdm.link/zohodev2dev
> _______________________________________________
> saxon-help mailing list archived at http://saxon.markmail.org/
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/saxon-help



--

"A false conclusion, once arrived at and widely accepted is not
dislodged easily, and the less it is understood, the more tenaciously
it is held." - Cantor's Law of Preservation of Ignorance.

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. http://sdm.link/zohodev2dev
_______________________________________________
saxon-help mailing list archived at http://saxon.markmail.org/
[hidden email]
https://lists.sourceforge.net/lists/listinfo/saxon-help 
Loading...