Project

Profile

Help

Bug #5641

closed

XQuery error leads to Java stack with internal error, sometimes

Added by Mary Holstege over 1 year ago. Updated about 1 year ago.

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

100%

Estimated time:
Legacy ID:
Applies to branch:
11, trunk
Fix Committed on Branch:
11, trunk
Fixed in Maintenance Release:
Platforms:
.NET, Java

Description

This is a little tricky to pin down: I have pruned the test case as much as I can.

It is definitely only on Saxon 11, not 10 (see saxon10.output.txt vs saxon11.output.txt). It is definitely an optimizer issue, as -opt:0 produces a good stack (see saxon11-noopt.output.txt) It is very sensitive to the details of the call chain (see comments in badframework.xqy)

What happens is that I have a bug in my XQuery code, but I get an ugly Java stack sans nice information on the (XQuery) stack frames.

Run the main fail.xqy


Files

saxon11-noopt.output.txt (1.14 KB) saxon11-noopt.output.txt Output in Saxon 11 with -opt:0 Mary Holstege, 2022-08-09 22:47
saxon11.output.txt (8.04 KB) saxon11.output.txt Output in Saxon 11 Mary Holstege, 2022-08-09 22:47
saxon10.output.txt (834 Bytes) saxon10.output.txt Output in Saxon 10 Mary Holstege, 2022-08-09 22:47
fail.xqy (571 Bytes) fail.xqy Main Mary Holstege, 2022-08-09 22:47
badframework.xqy (1.44 KB) badframework.xqy Imported module Mary Holstege, 2022-08-09 22:47

Please register to edit this issue

Also available in: Atom PDF