Adventures in concurrent tODE sessions: resume dbContinue:

[dalehenrich]

When resuming from a debugged session, the dbContinue message is sent in the context of a different UI process ... not in the context of the origin thread, so that the client side error handlers are not properly invoked.

Here's a client-side doit for Voyage that illustrated the problem (execute same code in two playgrounds after both debuggers come up resume the second debugger, then the first debugger and you will get a third debugger):

[ 
    VORepository current abort.
    Smalltalk at: #'_TUGRIK_X' put: '1'.
    self halt.
    VORepository current commit.
    Smalltalk at: #'_TUGRIK_X'
    ] voyageDoOnServer