��I'm sending this mail to the three lists because it is an error I found in the three Smalltalks (Squeak, Pharo and Cuis) and maybe we could share the effort to solve it and the solution.

��The problem can be reproduce with this test:

test1

self
should: [ self error: 'something' ]
raise: Error
withExceptionDo: [ :anError |
self assert: 'something different' equals: anError messageText ]

��If you run that test, it will fail of course. So if you go with the debugger to the context that signals de error (self error: 'something') and press restart and then over you will find the error. In the case of Squeak and Cuis, a new debugger is opened and you can not do anything with the original one. In the case of Pharo, the debugger stops working (in another try it opened a new debugger also but I could not reproduce it).

��I think the problem is related to the execution simulation but it is not a simple problem... Any idea what it could be?

Cheers!

Hernan.
--