[Mono-bugs] [Bug 77273][Cri] Changed - XSP icall.c warning

[bugzilla-daemon at bugzilla.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 joeshaw at novell.com.

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

--- shadow/77273	2006-02-08 14:52:15.000000000 -0500
+++ shadow/77273.tmp.4891	2006-02-09 18:07:03.000000000 -0500
@@ -10,12 +10,13 @@
 Component: Sys.Web
 AssignedTo: mono-bugs at ximian.com                            
 ReportedBy: carlos at applianz.com               
 QAContact: mono-bugs at ximian.com
 TargetMilestone: ---
 URL: 
+Cc: joeshaw at novell.com,tambet at ximian.com
 Summary: XSP icall.c warning
 
 XSP is all of the sudden going crazy for us. All we did is upgrade mono and
 XSP from 1.1.9.2 to 1.1.13.0 and now it keeps printing out this warning
 constantly that it never printed before:
 
@@ -99,6 +100,15 @@
 ------- Additional Comments From martin at ximian.com  2006-02-08 13:22 -------
 I already said before that I can't do anything about that without a
 testcase; reassigning to mono-bugs.
 
 ------- Additional Comments From gonzalo at ximian.com  2006-02-08 14:52 -------
 ->mono-bugs
+
+------- Additional Comments From joeshaw at novell.com  2006-02-09 18:07 -------
+I don't have an easy test case, but I can reproduce this reliably on
+my dual-CPU AMD 64 box running 1.1.13.2.  Running bludgeon (a beagle
+test program) triggers this warning and subsequent
+NullArgumentExceptions when calling System.Activator.CreateInstance().
+ We're not using any remoting.
+
+I'll try to get a stack trace