PR #3946 should be reverted; JVM `Process#waitFor` can validly return InterruptedException about scala-native HOT 2 OPEN

The change was introduced to improve debugging. When attaching the debugger to the process it would also receive the interrupt signal. It means that before we would be able to lookup the state of the program, it would already start executing the erroneous path of throwing the IOExceotion. Because the signal was delivered, but the isInterrupted flag of Java thread was not set up it means it was a spurious, unwanted interruption. In oppose to that thread.interrupt was send both signal and set the flag. In such case throwing exception on detected unwanted signal and restarting the waitFor seemed to be the most expected approach

from scala-native.

I suggest putting that behavior under a DEBUG flag/configuration_option and keeping the "normal" behavior
as specified by the JVM.

Thanks for the info.

from scala-native.