[Mono-bugs] [Bug 80799][Wis] Changed - Multithreaded App crashes in random locations

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Mon Feb 12 15:12:54 EST 2007

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 joncham at gmail.com.


--- shadow/80799	2007-02-12 15:08:34.000000000 -0500
+++ shadow/80799.tmp.12001	2007-02-12 15:12:54.000000000 -0500
@@ -131,6 +131,28 @@
 with a bit more confidence to classify where this bug should go.
 ------- Additional Comments From joncham at gmail.com  2007-02-12 15:08 -------
 Created an attachment (id=18678)
 pinvoke_crash.zip with test cases
+------- Additional Comments From joncham at gmail.com  2007-02-12 15:12 -------
+Added non-MWF test case zip file. Windows is where I reproduce this
+reliably. I could not reproduce on linux (but I didn't try very hard).
+Note in debugging, I find both threads in
+mono_marshal_get_native_wrapper, with one thread in side of the error
+if block 
+	if (!piinfo->addr) {
+		mono_mb_emit_exception (mb, exc_class, exc_arg);
+		csig = signature_dup (method->klass->image, sig);
+		csig->pinvoke = 0;
+		res = mono_mb_create_and_cache (cache, method,
+										mb, csig, csig->param_count + 16);
+		mono_mb_free (mb);
+		return res;
+	}
+The weird thing is that piinfo->addr != NULL but exc_class and exc_arg
+are, which have string functions called on them later and we die since
+the pointers are NULL.

More information about the mono-bugs mailing list