[Mono-bugs] [Bug 54813][Nor] Changed - mcs 0.30.1 crashes mono in metadata.c

[bugzilla-daemon@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 diltonm@mccomsoft.com.

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

--- shadow/54813	2004-03-04 13:48:18.000000000 -0500
+++ shadow/54813.tmp.31753	2004-03-04 18:01:33.000000000 -0500
@@ -1,8 +1,8 @@
 Bug#: 54813
-Product: Mono/Compilers
+Product: Mono: Compilers
 Version: unspecified
 OS: Fedora 1.0
 OS Details: Linux and Windows
 Status: REOPENED   
 Resolution: 
 Severity: Unknown
@@ -225,6 +225,46 @@
 one line for the C# compiler, can you share that?
 
 On the other hand, this might be a problem with us accessing the WSE.dll
 
 It would also be helpful if you run this in the debugger, and get a
 stack trace of when the problem happens at the assertion point.
+
+------- Additional Comments From diltonm@McCOMSoft.com  2004-03-04 18:01 -------
+>> I can not compile your program, since it uses the Microsoft WSE dll
+which I do not have.
+
+I go into the mcs.0xxx/class/Microsoft.Web.Services folder and run
+make. This outputs two Dlls to mcs.0.xxx/class/lib,
+Microsoft.Web.Services.1.dll and 2.dll. I then copy the 2.dll to
+Microsoft.Web.Services.dll in /usr/local/lib with the other Mono Dlls.
+
+
+>> You said that you had the problem down to
+one line for the C# compiler, can you share that?
+
+On 2-24 at 19:25
+Ok I isolated further and found that the following line was crashing 
+the compiler:
+
+//		private double _dTimerInterval = 1000 * Int32.Parse
+(Utility.GetAppSetting("Time Scaler"));
+
+
+>> On the other hand, this might be a problem with us accessing the
+WSE.dll
+
+It's possible but IIRC (and it's starting to get blurry) I had boiled
+the problem code down ao almost nothing. I belive it centers around
+calling a static routine in another DLL. Why my test code works not
+but my main project still fails with the same error is surprising.
+It's almost like a buffer is being overrun. Something DID change for
+the better between 0.30.1 and the latest CVS version.
+
+
+>> It would also be helpful if you run this in the debugger, and get a
+stack trace of when the problem happens at the assertion point.
+
+I've downloaded the debugger project from CVS and am attempting to
+build it now. If I can produce some useful information then I'll post it.
+
+Thanks.