Thanks, that works... now to make sense of all the debug stuff coming out ;) Thierry 2015-04-21 16:47 GMT+02:00 Pavel Krivanek <pavel.krivanek@gmail.com>:

You may use:

kill -USR1 <pid>

Cheers, -- Pavel

2015-04-21 16:36 GMT+02:00 Thierry Goubier <thierry.goubier@gmail.com>:

...

Hi all,

anybody knows if it would be possible to generate an external interruption (a signal) from outside the Pharo process which would trigger a Ctrl+. interrupt?

OSProcess 4.5.13 has a tendancy to lock the image on some linux systems (ubuntu 14.10 at least), and it would be nice to be able to interrupt it to be able to see where it is blocked.

"killall pharo" or Ctrl+C does not give much information :(

Thanks,

Thierry

Le 21/04/2015 18:04, Sean P. DeNigris a écrit :

Thierry Goubier wrote

...

OSProcess 4.5.13 has a tendancy to lock the image on some linux systems

Total shot in the dark, but IIRC setting PipeableOSProcess output to non blocking fixes many lockup scenarios

I believe downgrading OSProcess to 4.5.11 is making PipeableOSProcess use blocking I/O :) and it solves the lockup. Thierry