[Pharo-dev] Responsible development

Eliot Miranda eliot.miranda at gmail.com
Mon Dec 2 14:25:11 EST 2013


On Mon, Dec 2, 2013 at 6:47 AM, phil at highoctane.be <phil at 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 at gmail.com
> > wrote:
>
>> 2013/12/2 Pavel Krivanek <pavel.krivanek at 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20131202/4e23eb91/attachment-0002.html>


More information about the Pharo-dev mailing list