Project

Profile

Help

Actions
Send by e-mail Copy link

Bug #4779

closed

Bad command line parameters cause internal error and stack trace

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

Status:
Closed
Priority:
Low
Assignee:
Michael Kay
Category:
-
Sprint/Milestone:
-
Start date:
2020-10-04
Due date:
% Done:

100%

Estimated time:
Applies to JS Branch:
2
Fix Committed on JS Branch:
2
Fixed in JS Release:
Saxon-JS 2.1
SEF Generated with:
Platforms:
Company:
-
Contact person:
-
Additional contact persons:
-

Description

Incorrect parameter syntax on the xslt3 command line can trigger an internal error and a stack trace,

Example: a call with

xslt3 -xsl:xx.xsl.sef -s:samples.xml -o:out.xml -t  shigher-order-functions

Generates

Missing '=' in parameter 'shigher-order-functions'
Internal error: bad input to string constructor #undefined
Error
    at Object.$internalError$$ [as internalError] (/Users/mike/GitHub/saxon-js-enterprise/build/temp/js/build/SaxonJS2N.debug.js:886:56)
    at new $XdmString$$module$temp$js$source$src$XdmAtomic$ (/Users/mike/GitHub/saxon-js-enterprise/build/temp/js/build/SaxonJS2N.debug.js:1346:72)
    at Object.fromString (/Users/mike/GitHub/saxon-js-enterprise/build/temp/js/build/SaxonJS2N.debug.js:2043:12)
    at /Users/mike/GitHub/saxon-js-enterprise/build/temp/js/build/xslt3ee.js:46:228
    at Array.forEach (<anonymous>)
....etc

Please register to edit this issue

Actions
Send by e-mail Copy link

Also available in: Atom PDF Tracking page