Hi,

I've just come across this unexpected behavior: 
1. open Debugger on 1+1
2. step through until you get on Processor activeProcess
3. step into activeProcess
4. hit Proceed and you get a BCR error

Similarly if you:
1. open Debugger on Processor activeProcess suspend
2. step into activeProcess
4. hit Proceed and you get an unresponsive image (UI suspended) - you can recover via Alt+.

In all other cases when you avoid stepping into activeProcess method debugging just finishes fine... 

Is this something to worry about or is this an expected behavior given the nature of the activeProcess method?

Thanks,

^[^ Jaromir
  --

Sent from Squeak Inbox Talk