On 11/29/2012 01:57 PM, Göran Krampe wrote:
On 11/29/2012 01:51 PM, Torsten Bergmann wrote:
Same issue with Stack VM. So it looks like it
is image side.
Yes, stackVM did not help, at least not with Pharo 2.0.
When the keyboard focus is in a workspace and
I hit CMD+. it not directly interrupts. Only
when I repeat very often.
I've put a
Transcript show: toInterrupt asString; cr.
into UserInterruptHandler>>handleUserInterrupt and
very often this block temporary variable is nil since
#processToInterrupt returns nil.
Sometimes the #processToInterrupt catches
a process to interrupt and then the debugger opens.
Göran can you confirm that as well?
Yes, similar behavior. I also noticed that Pharo (compared to Squeak)
does not send #primInterruptSemaphore: ...
Not sure if related, but perhaps.
regards, Göran
