Raul Acevedo wrote: > Would the problem be "solved" if comint returned code 1, instead of 129? > > In other words, is the problem that comint returns an inappropriate > error code, or that comint returns *any* error code at all (i.e. it > shouldn't get an error from the subprocess in the first place)?
I think the latter. The bug typically bites me when running JUnit tests and it's clear (based on the expected output) that either the process terminates early, or a large part of the output is just lost. Cheers, Len.
