Bug 27313

Bug: 27313

Impact:

Product:

GemBuilder for Smalltalk

Versions:

7.1.2, 7.1.1, 7.1, 7.0.2, 7.0.1, 7.0, 5.2.3, 5.2.2, 5.2.1, 5.2

Platform:

VW 5i

Fixed In:

VW 5i GBS debugger: No method was found for the selector #stackDepth

If you are stepping through GemStone code in a VW GBS debugger,
and use the "send" button to step into a message that raises a
new exception, a new notifier pops up with:

Unhandled GemStone Error - rtErrDoesNotUnderstand - No method was found for the
+selector #stackDepth when sent to nil with arguments contained in anArray( ).

The stack looks like this:

  'Unhandled GemStone Error - rtErrDoesNotUnderstand'
  GS: System class | signal:args:signalDictionary:
  GS: UndefinedObject (Object) | doesNotUnderstand:
  GS: UndefinedObject (Object) | _doesNotUnderstand:
  GbsObject>>privatePerform:withArgs:
  GbsObject>>privatePerform:
  GbxActivation>>reset
  optimized [] in GbxActivation class>>fromProcess:atLevel:
  BlockClosure>>ensure:
  Cursor>>showWhile:
  GbsSessionManager>>showBusyWhile:
  GbxActivation class>>fromProcess:atLevel:
  GbsError>>activationAt:
  GbxDebugger>>gbxUnexpectedGSError:
  optimized [] in GbxDebugger>>gbxGsSend
  ...

The GbxActivation's "process" is Onil - GbxActivation>>reset
is sending #stackDepth to it.

Workaround:

If you just close the new notifier, the original debugger
appears to be healthy.

If you "step" into another exception instead of "send", it
works.