On Sun, Dec 23, 2007 at 11:12:38PM -0800, John M McIntosh wrote:
> I've build a new OSProcessPlugin  (4.2.4)
> 
> http://wiki.squeak.org/squeak/3349  and
> 
> a newly generated AioPlugin V2.2
> 
> http://wiki.squeak.org/squeak/3384
> 
> for testing purposes. If someone can test them on os-x 10.3, 10.4 on  
> macintel and powerpc, that would be helpful.

Hi John,
Thanks for doing this. I've borrowed a Mac laptop - very nice machine
BTW - and downloaded your test bundles. I fumbled around enough to get
Squeak running (all of this user friendly stuff is rather jarring at
first). Imagine my surprise when CommandShell just up and worked.

I'm not sure how to identify this machine, but it's Intel-based and
according to 'uname -a' it is this:

Darwin colleen-moynihans-computer.local 8.10.1 Darwin Kernel Version 8.10.1: Wed May 23 16:33:00 PDT 2007; root:xnu-792.22.5~1/RELEASE_I386 i386 i386

> This means the CommandShell Sunits now mostly run (1 failure) on the  
> macintosh carbon based VM, well
> at least on os-x 10.5.1 on macintel.

I've made updates to the CommandShell and OSProcess tests cases to address
problems with OS X path name and file protection conventions versus
vanilla Unix/Linux. The updates are on SqueakSource (but not SqueakMap
or Universes yet). At this point we have:

Tests-CommandShell all pass (!)
  CommandShellTestCase => green
  ExpressionEvaluatorTestCase => green
  InternalPipeTestCase => green
  PipelineEventsTestCase => green
  ShellSyntaxTestCase => green

Tests-OSProcess, some pass:
  AioEventHandlerTestCase => green
  OSPipeTestCase => green
  UnixProcessAccessorTestCase => green after fixes, see SqueakSource
  UnixProcessFileLockTestCase => green

The following crash the VM due to #forkSqueak issues on OS X:
  UnixProcessUnixFileLockingTestCase
  UnixProcessWin32FileLockingTestCase
  UnixProcessTestCase

> Please note not all of the OSProcess tests will run, some cause the VM  
> to crash when they attempt to fork the VM since
> forking the carbon based VM is not allowable.  Corrupts memory and  
> crashes really fast.

The #forkSqueak problem is nasty and unfortunate. At the very least we
don't want it crashing the VM. I haven't figured out how to compile
things on a Mac yet, but if I get some more time with this OS X laptop
I'd like to figure it out and maybe inject some more sensible behavior
into #forkSqueak.

Dave