I tried it on my dual core intel mac (older 32 bit one), and the VM (Squeak4.3.1 Beta1U) crashed. So I loaded the OSProcess tests into an up to date trunk image, and running the tests in UnixProcessTestCase crashed the VM. This also happens in the Pharo Dev 1.0 RC2.<br>
<br>Mike<br><br><br clear="all">Mike Hales<br>Engineering Manager<br>KnowledgeScape<br><a href="http://www.kscape.com">www.kscape.com</a><br>
<br><br><div class="gmail_quote">On Tue, Jan 26, 2010 at 3:35 PM, David T. Lewis <span dir="ltr"><<a href="mailto:lewis@mail.msen.com">lewis@mail.msen.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div><div></div><div class="h5">On Tue, Jan 26, 2010 at 08:19:14PM -0200, Jecel Assumpcao Jr wrote:<br>
> David,<br>
><br>
> I took a quick look on a quad core 2 box running Fedora Core 10 and the<br>
> Squeak 3.7-7 VM and 3.10.2 image. It seems to lock up on "RemoteTask<br>
> result". Running the Tests-OSProcess does indeed cause one failure in<br>
> #testCooperatingProcesses04 where the tests for version 43 were all<br>
> green. Running Tests-CommandShell locks up after 71 tests with one<br>
> failure (version 4.3 had all green tests after I created a /usr/bin/vi<br>
> file).<br>
<br>
</div></div>Jecel,<br>
<br>
Thanks very much for trying this and for the feedback. I guess it's<br>
about time I replaced my ten year old computer so I can test this myself.<br>
I am guessing that a possible culprit is signal delivery for the SIGCHLD<br>
handler, I wonder if that might behave a little differently on a<br>
multi-core machine ...<br>
<br>
Thanks again,<br>
<br>
Dave<br>
<br>
<br>
</blockquote></div><br>