[Mono-bugs] [Bug 50049][Maj] Changed - MonoThread domain-specific handling broken

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Thu, 23 Oct 2003 14:20:53 -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 gonzalo@ximian.com.


--- shadow/50049	2003-10-23 11:10:23.000000000 -0400
+++ shadow/50049.tmp.24363	2003-10-23 14:20:53.000000000 -0400
@@ -2,24 +2,27 @@
 Product: Mono/Runtime
 Version: unspecified
 OS: other
 OS Details: 
 Status: NEW   
+Severity: Unknown
 Priority: Major
 Component: misc
 AssignedTo: dick@ximian.com                            
 ReportedBy: lupus@ximian.com               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
 Summary: MonoThread domain-specific handling broken
 MonoThread is the unmanaged representation for the Thread object.
 The runtime should make sure the current MonoThread corresponds to the
 current domain, both in the finalizer thread and when appdomain changes
 happen. Currently, at least for the finalizer thread, the MonoThread object
 is not set, causing nullref exceptions when executing finalizers. If the
 object is not set correctly on domain changes it will cause random
 hard-to-track bugs, hence this is a major bug.
+------- Additional Comments From gonzalo@ximian.com  2003-10-23 14:20 -------
+Threads in the threadpol change the domain to the one of the
+IAsyncResult, but don't do anything else. What should I do?