Bug #4050: Internal error : net.sf.saxon.value.StringValue cannot be cast to net.sf.saxon.om.NodeInfo - Saxon - Saxonica Developer Community

Actions

Send by e-mail Copy link

Bug #4050

closed

Internal error : net.sf.saxon.value.StringValue cannot be cast to net.sf.saxon.om.NodeInfo

Added by Michael Kay over 5 years ago. Updated about 5 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Michael Kay

Category:

XSLT export

Sprint/Milestone:

Start date:

2018-11-25

Due date:

% Done:

100%

Estimated time:

Legacy ID:

Applies to branch:

9.9

Fix Committed on Branch:

9.9

Fixed in Maintenance Release:

9.9.1.1

Platforms:

Description

The error occurs when compiling the xslt-compiler-in-xslt starting with a SEF file produced by the xslt-compiler-in-java.

That is, transform

-xsl:XSLT-SEF-compiler.xsl -s:XSLT-SEF-compiler.xsl -im:compile-complete -export:Users/mike/Desktop/temp/compiler.sef

then

-xsl:/Users/mike/Desktop/temp/compiler.sef -s:XSLT-SEF-compiler.xsl -im:compile-complete -o:/Users/mike/Desktop/temp/compiler2.sef -t --generateByteCode:off

Actions

Copy link

Updated by Michael Kay over 5 years ago

The function in question performs indexed access to the sequence supplied as the second argument. When this happens, and the supplied value is not already an indexed value, the code for evaluating an IndexedFilterExpression modifies the argument value in-situ to be an IndexedValue equivalent to the value supplied. It is identifying the stack location to overwrite based on the slot number held in the UserFunctionParameter object referenced from the LocalVariableReference. But the slot number in the UserFunctionParameter is not being set up when a SEF file is reloaded, so the wrong stack slot is overwritten.

Actions

Copy link