[Mono-bugs] [Bug 77393][Wis] New - System.Diagnostics.Process.Start problems

[bugzilla-daemon at bugzilla.ximian.com]

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 dominic_ullmann at hispeed.ch.

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

--- shadow/77393	2006-01-28 09:13:49.000000000 -0500
+++ shadow/77393.tmp.23756	2006-01-28 09:13:49.000000000 -0500
@@ -0,0 +1,145 @@
+Bug#: 77393
+Product: Mono: Runtime
+Version: 1.1
+OS: 
+OS Details: Ubuntu Linux 5.04
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Wishlist
+Component: io-layer
+AssignedTo: dick at ximian.com                            
+ReportedBy: dominic_ullmann at hispeed.ch               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: System.Diagnostics.Process.Start problems
+
+Description of Problem:
+For automatic client/server integration tests, I use a small utility
+written in C#, which starts the server process in the background.
+
+Sometimes, it works correctly, at other times I get one of two problems:
+
+First problem:
+WARNING **: process_set_current: error looking up process handle 0x403
+
+In this case, Process.GetProcessById (used in a second tool to kill a
+process) is not able to find the server process with the given id. In the
+top utility, the mono process running the server is listed with this id.
+
+Second problem: SIGSEGV
+
+=================================================================
+Got a SIGSEGV while executing native code. This usually indicates
+a fatal error in the mono runtime or one of the native libraries
+used by your application.
+=================================================================
+
+Stacktrace:
+
+
+Native stacktrace:
+
+        /devel/bin/mono(mono_handle_native_sigsegv+0xc0) [0x813cdd0]
+        /devel/bin/mono [0x8129216]
+        [0xffffe440]
+        /devel/bin/mono [0x80f0a11]
+        /devel/bin/mono(mono_once+0xb4) [0x80ef694]
+        /devel/bin/mono [0x80f0b4c]
+        /devel/bin/mono(mono_runtime_init+0xc4) [0x80bdf44]
+        /devel/bin/mono [0x812a1b2]
+        /devel/bin/mono(mono_main+0x194) [0x805d274]
+        /devel/bin/mono [0x805c2ab]
+        /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xf8) [0xb7df28c8]
+        /devel/bin/mono [0x805c1e1]
+
+I used this launch utility on ms.net for years without any problems. It
+seemed to work also nice on earlier mono 1.1 versions. Currently, I'm using
+mono 1.1.13.2.
+
+Steps to reproduce the problem:
+For simplicity, I use the launch utility to launch itself in a new process.
+Sadly, the problems occur in this case less frequently than when launching
+my test servers.
+1. compile the attached utility mcs launch.cs
+2. run the utility in the following way:
+mono launch.exe mono launch.exe
+
+Actual Results:
+Sometimes
+
+=================================================================
+Got a SIGSEGV while executing native code. This usually indicates
+a fatal error in the mono runtime or one of the native libraries
+used by your application.
+=================================================================
+
+Stacktrace:
+
+
+Native stacktrace:
+
+        /devel/bin/mono(mono_handle_native_sigsegv+0xc0) [0x813cdd0]
+        /devel/bin/mono [0x8129216]
+        [0xffffe440]
+        /devel/bin/mono [0x80f0a11]
+        /devel/bin/mono(mono_once+0xb4) [0x80ef694]
+        /devel/bin/mono [0x80f0b4c]
+        /devel/bin/mono(mono_runtime_init+0xc4) [0x80bdf44]
+        /devel/bin/mono [0x812a1b2]
+        /devel/bin/mono(mono_main+0x194) [0x805d274]
+        /devel/bin/mono [0x805c2ab]
+        /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xf8) [0xb7df28c8]
+        /devel/bin/mono [0x805c1e1]
+
+and sometimes
+
+mono launch.exe mono launch.exe
+13155
+** (launch.exe:13155): WARNING **: process_set_current: error looking up
+process handle 0x403
+Error: programm to launch is missing
+
+Usage:
+Lauch [options] name [args]
+
+options are:
+-h              help
+-d directory    the working directory for programm to start
+-w              start not minimized, but normal
+
+sometimes the expected result output.
+
+
+Expected Results:
+The launch utility prints the pid of the new process. The new process
+prints its error message.
+
+13067
+Error: programm to launch is missing
+
+Usage:
+Lauch [options] name [args]
+
+options are:
+-h              help
+-d directory    the working directory for programm to start
+-w              start not minimized, but normal
+
+
+How often does this happen? 
+Sometimes. For my test server in one of four cases. For the  test utility
+in one of 15 cases.
+
+Additional Information:
+Running the utility from inside a Makefile seems to increase the number of
+the process_set_current problem. 
+When not started by a make, the SIGSEGV problem seems to be more likely.
+
+If you would provide some hints on how to debug this problem, I can try to
+provide more information on this problem.
+
+Attached file:
+launch.cs