Manual and release notes for upcoming 10.2.0

[Lutz]

Put 'println' statements at the beginning of both 'dolist' loops (tag and _@) and see what is going on. This will show you the path of execution and the reason for the overflow message. Note that only callstack depth is reflected in 'sys-info' and only before the error occurs. The error itself will cause a stack cleanup. The result stack cannot be traced with 'sys-info'.



The other possibility would be:

Code Select Expand

(debug (eval xf))

to see what is happening.

[cormullion]

Thanks, Lutz. Which is the call stack depth - (sys-info 4) (= "Environment stack level")? This is nearly always 0, and occasionally 1.



It says this just before the call or result stack overflow



(86755 268435456 449 10 0 2048 0 60948 10201 131)



I've gone through with the debugger - just can't work out what I should be looking for. The code is simple, but fails after about 21000 function calls.