On Mon, Dec 2, 2013 at 6:47 AM, phil@highoctane.be <phil@highoctane.be>wrote:
As Clement explained to be, the Cmd + . combo is only tested on VM bytecode "backjumps".
It is also tested on every non-primitive send.
So, if the bytecode is stuck with no backjumps, it is definitely stuck.
I'd like to see where this occurs in the VM (maybe in the hope I could have a slow, but interruptible VM at all times) - this could take the form of a setting that gets turned on.
You can always send SIGUSR1 to the VM on linux and Mac OS. You'll need to open the console to see the output unless you run the VM from a terminal. But you can find out what it's doing.
Phil
On Mon, Dec 2, 2013 at 3:30 PM, Esteban A. Maringolo <emaringolo@gmail.com
wrote:
2013/12/2 Pavel Krivanek <pavel.krivanek@gmail.com>:
User interrupt (cmd + .) was not working?
Most of the times for simple things it does, but sometimes it doesn't.
Regards,
Esteban A. Maringolo
-- best, Eliot