Interpreter: Internal errors are reported as "internal error" but could have displayed the real problem description

[lausdahl]

The handling of internal errors in the interpreter is not useful since it just displays "internal error" but in many cases it might be e.g. a stack overflow indicating that a recursive function in a model may need a bigger stack size.

See the MainThread.java and search for "internal error" e.g:

overture/core/interpreter/src/main/java/org/overture/interpreter/scheduler/MainThread.java

Line 106 in 93290ef

setException(new Exception("internal error", e));

If a stack overflow exception is thrown it just shows "internal error" in the debugger by sending the following messages:

<?xml version="1.0" encoding="UTF-8"?><response command="run" transaction_id="120"><error code="206" apperr=""><message>internal error</message></error></response>

<?xml version="1.0" encoding="UTF-8"?><response command="stack_get" transaction_id="121"><error code="5" apperr=""><message>stack_get -i 121</message></error></response>

but it could have done better since the exception it caught was a stackoverflow inner exception.

[lausdahl]

Have created this issue for the inconvenient reporting of errors in the AGCO model on certain Java installations with a too small Xss @pglvdm

[nickbattle]

This enhancement has been fixed in #709.