#20 IOException after launching UnitTest executable

[Gerhard H. Leonhartsberger]

eclipse.buildId=I20080617-2000
java.version=1.5.0_13
java.vendor=Apple Inc.
BootLoader constants: OS=macosx, ARCH=ppc, WS=carbon, NL=en_US
Framework arguments: -product org.eclipse.sdk.ide
Command-line arguments: -product org.eclipse.sdk.ide -data /Users/local-home/gerhard/Development/Workspace/../runtime-New_configuration -dev file:/Users/local-home/gerhard/Development/Workspace/.metadata/.plugins/org.eclipse.pde.core/Ecut/dev.properties -os macosx -ws carbon -arch ppc

Error
Sat Sep 13 17:00:03 CEST 2008
Error logged from Debug Core:

java.io.IOException: close error
at org.eclipse.cdt.utils.spawner.SpawnerOutputStream.close(SpawnerOutputStream.java:71)
at org.eclipse.debug.internal.core.InputStreamMonitor.write(InputStreamMonitor.java:113)
at org.eclipse.debug.internal.core.InputStreamMonitor$1.run(InputStreamMonitor.java:84)
at java.lang.Thread.run(Thread.java:613)

[Gerhard H. Leonhartsberger]

The exception occurs on MacOS X. There is no IOException on windows platform

[Gerhard H. Leonhartsberger]

The current implementation of the EcutProtocol should be reworked. As it is still based on the old cdt.cppunit implementation for the following reasons:
- processMessage() is invoked to often when a test case reports an error/failure.
- The method body is unnecessary complex.
- the ECUT protocol is not easily understandable.