Debugger evaluation containing an explicit return results in error or corrupts variable values
If a GemStone smalltalk expression is executed while in a GemStone context in the debugger, using GS-do it, GS-Print it, or GS-Inspect it, and the code includes an explicit return (^), execution results are not correct.
In most cases, this results in a subscript out of bounds error. In the case of evaluations that affect method variables in the debugger, however, this may corrupt the values of the temporary variables in the debugger.
Workaround
Avoid executing code containing explicit returns within the debugger.
Last updated: 11/2/16