[Mono-bugs] [Bug 52673][Cri] New - .ctor AppDomain ThreadPool exceptions

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Wed, 7 Jan 2004 22:38:44 -0500 (EST)

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 derek.mcumber@datamtnsol.com.


--- shadow/52673	2004-01-07 22:38:44.000000000 -0500
+++ shadow/52673.tmp.17005	2004-01-07 22:38:44.000000000 -0500
@@ -0,0 +1,89 @@
+Bug#: 52673
+Product: Mono/Runtime
+Version: unspecified
+OS Details: 
+Status: NEW   
+Priority: Critical
+Component: misc
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: derek.mcumber@datamtnsol.com               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+Summary: .ctor AppDomain ThreadPool exceptions
+Please fill in this template when reporting a bug, unless you know what you
+are doing.
+Description of Problem:
+On Windows xp/2k and Win98, there is still some difficulty with the
+threadpool.c code and the AppDomain changes.  I have tried different
+combinations of mono and threadpool.c file, but no luck.
+Steps to reproduce the problem:
+1. Compile the TestMonoWeb code in the
+          mcs-0.2X\class\System.Web\Test\TestMonoWeb
+2. Run it on a flavor of mono you think should work
+3. Let me know if there is a combination that succeeds.
+If I can get some of my threadpool changes stable, I will
+attach them.
+Actual Results:
+WinXP with Mono-0.29(from new .exe install):
+Unhandled Exception: System.Web.HttpException: Cannot get .appPath
+in <0x00090> System.Web.Hosting.SimpleWorkerRequest:.ctor
+in <0x000ae> TestMonoWeb.Test1:Main (string[])
+Unhandled Exception: System.Web.HttpException: Cannot get .appPath
+in <0x00090> System.Web.Hosting.SimpleWorkerRequest:.ctor
+in <0x000ae> TestMonoWeb.Test1:Main (string[])
+Mono-0.28/Win98 with unicows.dll:
+Unhandled Exception: System.ExecutionEngineException: SIGILL
+in (unmanaged) (wrapper remoting-invoke) System.Object:GetType ()
+in <0x00004> (wrapper remoting-invoke) System.Object:GetType ()
+in <0x0002f> (wrapper remoting-invoke-with-check) System.Object:GetType ()
+in <0x00021> System.Type:IsInstanceOfType (object)
+in <0x0010d> System.Runtime.Remoting.Proxies.RealProxy:ProcessResponse
+in <0x0010d> System.Runtime.Remoting.Proxies.RealProxy:PrivateInvoke
+in (unmanaged) (wrapper remoting-invoke) System.AppDomain:CreateInstance
+in <0x00004> (wrapper remoting-invoke) System.AppDomain:CreateInstance
+in <0x0003d> (wrapper remoting-invoke-with-check)
+System.AppDomain:CreateInstance (string,string)
+in <0x0006e> System.Web.Hosting.ApplicationHost:InitConfigInNewAppDomain
+in <0x0043f> System.Web.Hosting.ApplicationHost:CreateApplicationHost
+in <0x00043> TestMonoWeb.Test1:Main (string[])
+Expected Results:
+ThreadPool to accept Thread.SetData/TlsSetValue and GetValue objects being
+in different domains.
+How often does this happen? 
+every time
+Additional Information:
+It appears to be related 50049