[Mono-bugs] [Bug 45302][Cos] Changed - Mono should throw bug when getting exit code of unfinished process

bugzilla-daemon@rocky.ximian.com bugzilla-daemon@rocky.ximian.com
Wed, 25 Jun 2003 14:58:50 -0400 (EDT)


Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by gert.driesen@pandora.be.

http://bugzilla.ximian.com/show_bug.cgi?id=45302

--- shadow/45302	Tue Jun 24 19:26:01 2003
+++ shadow/45302.tmp.21468	Wed Jun 25 14:58:50 2003
@@ -102,6 +102,21 @@
 Yes
 
 >Does it return exit code 0 when you set the milliseconds 
 >argument in WaitForExit to Int32.MaxValue ?
 
 Yes
+
+------- Additional Comments From gert.driesen@pandora.be  2003-06-25 14:58 -------
+I've rebuild Mono from cvs, and when I specify In32.MaxValue as
+timeout in WaitForExit in the test case I provided, the process exits
+immediately with exit code 259.
+
+While running external processes as part of NAnt, I still get mixed
+results when if used Int32.MaxValue as timeout.  Sometimes it actually
+returns exit code 0, but most of the time it returns exit code 259.
+But when I specify a lower timeout eg. 8000 milliseconds everything
+works fine.
+
+So I assume Process.WaitForExit doesn't handle Int32.MaxValue as
+timeout very well.
+