[Mono-bugs] [Bug 31817][Nor] Changed - exceptions not properly handled in therads with mono

[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 vladimir@pobox.com.

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

--- shadow/31817	Sun Oct  6 04:05:32 2002
+++ shadow/31817.tmp.3238	Sun Oct  6 06:02:37 2002
@@ -1,13 +1,13 @@
 Bug#: 31817
 Product: Mono/Runtime
 Version: unspecified
 OS: unknown
 OS Details: 
-Status: NEW   
-Resolution: 
+Status: RESOLVED   
+Resolution: FIXED
 Severity: Unknown
 Priority: Normal
 Component: misc
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: vladimir@pobox.com               
 QAContact: mono-bugs@ximian.com
@@ -134,6 +134,28 @@
 in 6.1alpha5.
 mono is being compiled with -DGC_LINUX_THREADS, as per lupus' patch of
 two weeks ago.
 running with GC_NO_GC has no effect (still the segfault)
 
 still poking...
+
+------- Additional Comments From vladimir@pobox.com  2002-10-06 06:02 -------
+I would like to close this bug with "REPORTERISAMORON", but that
+doesn't seem to be an option.  In trying to fix the build issues with
+automake-1.6, I added libmono.la to mono's list of libraries to link
+with.  (See patch sent to mono-hackers-list a few days ago.)  However,
+I neglected to remove the previous set of .la's that were there --
+which were already being linked in to libmono.la (I assume I did not
+notice this at the time).  The net result was behaviour such as:
+
+(gdb) p { &slothash_key, &current_object_key, &appdomain_thread_id }
+$130 = {0x80aab0c, 0x80aab08, 0x80a7e34}
+in the main thread, and
+
+(gdb) p { &slothash_key, &current_object_key, &appdomain_thread_id }
+$4 = {0x400f2280, 0x400eeedc, 0x80a7e34}
+in any threads other than the main thread (due to the way the symbols
+were resolved in the lwp/thread).
+
+Removing all .la's but libmono.la from mono's link line fixes the problem.
+
+