You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by bu...@apache.org on 2003/06/04 10:55:10 UTC
DO NOT REPLY [Bug 5003] -
exec task does not return after executed command finished on Windows only
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5003>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5003
exec task does not return after executed command finished on Windows only
------- Additional Comments From levylambert@tiscali-dsl.de 2003-06-04 08:55 -------
It works for me with :
java version "1.4.1_01"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_01-b01)
Java HotSpot(TM) Client VM (build 1.4.1_01-b01, mixed mode)
on
Win 2K, Service Pack 2
However, I wonder whether what is really happening is not that rmid has been
fixed to close its stdout and stderr properly.
I tried also with cvs log (which I am doing over ssh), and did not reproduce the
problem.
So the next question is :
how can one create a test class or a shell or Perl script or C program which
does not close properly its stdin/stderr streams, so that the problem can be
"lab studied" ?
Without a possibility to reproduce the problem, this should be closed as WONTFIX
or WORKSFORME.