[Vm-dev] [Pharo-dev] Problem with OSSubprocess / signals / heartbeat ?

Esteban Lorenzano estebanlm at gmail.com
Wed Mar 29 07:37:35 UTC 2017


> On 29 Mar 2017, at 02:02, Ben Coman <btc at openInWorld.com> wrote:
> 
> 
> On Fri, Feb 24, 2017 at 11:57 AM, Holger Freyther <holger at freyther.de> wrote:
>> 
>> 
>>> On 21 Dec 2016, at 22:29, Guille Polito <guillermopolito at gmail.com> wrote:
>>> 
>> 
>> 
>> Hi!
>> 
>>> Now, this heartbeat threaded VM is the recommended in the README file, and we see that OSSubprocess generates the exact issue stated. The main problem remains for the moment since Pharo's default download includes not this VM but the itimer one. I talked with Esteban about it and he was aware of these two VM flavours, and the reason why we are using the itimer one is the need to deploy those permission files in /etc, which makes installation a bit less automatic.
>> 
>> It is not a matter of configuration, e.g. more infrastructure is migrated into docker containers (I run the CI with docker containers) and even as root inside the container you might not be allowed to use realtime priority. And you might not be able to influence how your container is being executed.
>> 
>> holger
>> 
>> PS: Have you seen the fix David Lewis made to the UnixProcess plugin, maybe it already helps with your bug as well?
> 
> If these two commits work out, the threaded VM may become a viable
> default option...
> https://github.com/OpenSmalltalk/opensmalltalk-vm/commit/32f321583c69ca27e61ffaff6decc2a3e4b6ca5e <https://github.com/OpenSmalltalk/opensmalltalk-vm/commit/32f321583c69ca27e61ffaff6decc2a3e4b6ca5e>

I think this change restores a cleanup introduced by Eliot (nuke all those #define and change it by exeName).

Esteban

> https://github.com/OpenSmalltalk/opensmalltalk-vm/commit/5418a415e9297f601f6d57ee732fd7fd942da08c
> 
> cheers -ben

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/vm-dev/attachments/20170329/c00080d1/attachment.html>


More information about the Vm-dev mailing list