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 [EMAIL PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=77273 --- shadow/77273 2006-01-15 22:23:43.000000000 -0500 +++ shadow/77273.tmp.4666 2006-01-15 22:23:43.000000000 -0500 @@ -0,0 +1,83 @@ +Bug#: 77273 +Product: Mono: Class Libraries +Version: 1.1 +OS: +OS Details: +Status: NEW +Resolution: +Severity: +Priority: Wishlist +Component: Sys.Web +AssignedTo: [EMAIL PROTECTED] +ReportedBy: [EMAIL PROTECTED] +QAContact: [EMAIL PROTECTED] +TargetMilestone: --- +URL: +Cc: +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: + + + +** (/usr/local/lib/xsp/1.0/xsp.exe:15518): WARNING **: icall.c:1020 + +** (/usr/local/lib/xsp/1.0/xsp.exe:15520): WARNING **: icall.c:1020 + +** (/usr/local/lib/xsp/1.0/xsp.exe:15518): WARNING **: icall.c:1020 + +** (/usr/local/lib/xsp/1.0/xsp.exe:15515): WARNING **: icall.c:1020 + +** (/usr/local/lib/xsp/1.0/xsp.exe:15518): WARNING **: icall.c:1020 + +** (/usr/local/lib/xsp/1.0/xsp.exe:15515): WARNING **: icall.c:1020 + +** (/usr/local/lib/xsp/1.0/xsp.exe:15518): WARNING **: icall.c:1020 + +** (/usr/local/lib/xsp/1.0/xsp.exe:15515): WARNING **: icall.c:1020 + +** (/usr/local/lib/xsp/1.0/xsp.exe:15515): WARNING **: icall.c:1020 + +** (/usr/local/lib/xsp/1.0/xsp.exe:15518): WARNING **: icall.c:1020 + +** (/usr/local/lib/xsp/1.0/xsp.exe:15515): WARNING **: icall.c:1020 + + + +On the mailing list Richard Torkar replied to me with the following +message, I am guessing it will help: + +=================================== + +I don't know if it's any help to you but it looks like the mono runtime +gives you that msg. If you look in icall.c on line 1020 you see this: + /* + * FIXME: mono_method_get_last_managed() sometimes returns +NULL, thus + * causing +ves_icall_System_Reflection_Assembly_GetCallingAssembly() + * to crash. This only seems to happen in some +strange remoting + * scenarios and I was unable to figure out what's +happening there. + * Dec 10, 2005 - Martin. + */ + + if (dest) + assembly = dest->klass->image->assembly; + else { + g_warning (G_STRLOC); + } + +The last line: g_warning, is the one that prints the warning. Martin seems +to be aware of this "bug" since he wrote that comment Dec 10. Maybe ask him +(could it be Martin Baulig you're after? Not sure.) + +=================================== + +The code I have on XSP has a lot of remoting, some objects are marshal by +ref with infinite lifespans, some of them are created by the webservices +inside xsp and used by an outside application and some other objects are +created by an application outside of xsp and used by the webservices in xsp. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
