When a stack overflow stops the rexx interpreter, it finishes orderly with error 11.1, see test script below.
When the interpreter is called via API (through BSF4ooRexx), SIGNAL does not trap the error and the JNI crashes, see attached usenet post.
Rony replied that the error lies in the API, NewRoutine() and CallRoutine() :
Running your Rexx program with rexx.exe directly, indeed yields that particular syntax error,
whereas running it via the ooRexx APIs (the NewRoutine()-API immediately followed by the
CallRoutine()-API) does not.
Do you agree , is there more evidence necessary before you can look into the subject matter ?
signal on any name error
say 'REXX START'
crash: call crash
say 'REXX ERROR'