[Mono-bugs] [Bug 31265][Maj] Changed - Problems with GCHandle

[bugzilla-daemon@rocky.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 dick@ximian.com.

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

--- shadow/31265	Fri Nov 15 06:11:56 2002
+++ shadow/31265.tmp.23358	Mon Nov 18 10:44:52 2002
@@ -1,13 +1,13 @@
 Bug#: 31265
 Product: Mono/Runtime
 Version: unspecified
 OS: Red Hat 6.2
 OS Details: Kernel 2.4.2
-Status: RESOLVED   
-Resolution: FIXED
+Status: REOPENED   
+Resolution: 
 Severity: Unknown
 Priority: Major
 Component: misc
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: ztashev@openlinksw.co.uk               
 QAContact: mono-bugs@ximian.com
@@ -57,6 +57,21 @@
 
 ------- Additional Comments From ztashev@openlinksw.co.uk  2002-09-30 03:54 -------
 Yes of course.
 
 ------- Additional Comments From dick@ximian.com  2002-11-15 06:11 -------
 Fixed by Tim Haynes
+
+------- Additional Comments From dick@ximian.com  2002-11-18 10:44 -------
+The weak references patch seems to be causing segfaults deep inside
+libgc.  With the threaded finalizer, bug 31333 is now fixed, but only
+if I revert the line:
+
+- if (((gulong)new_array [i]) & 0x1) {
++ if ((gc_handle_types[i] == HANDLE_WEAK) || (gc_handle_types[i] ==
+HANDLE_WEAK_TRACK)) {
+
+in ves_icall_System_GCHandle_GetTargetHandle().
+
+I assume the code will break without the threaded finalizer, but the
+test is deadlocking too soon to show it.
+