[Mono-bugs] [Bug 81956][Nor] Changed - ArrayOutOfBounds in BigInteger class

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Mon Aug 13 14:10:42 EDT 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 sebastien at ximian.com.


--- shadow/81956	2007-08-04 14:48:38.000000000 -0400
+++ shadow/81956.tmp.13451	2007-08-13 14:10:42.000000000 -0400
@@ -1,22 +1,21 @@
 Bug#: 81956
 Product: Mono: Class Libraries
 Version: 1.2
 OS: unknown
 OS Details: 
-Status: NEW   
+Status: NEEDINFO   
 Severity: Unknown
 Priority: Normal
 Component: Mono.Security
 AssignedTo: sebastien at ximian.com                            
 ReportedBy: alan.mcgovern at gmail.com               
 QAContact: mono-bugs at ximian.com
 TargetMilestone: ---
 Summary: ArrayOutOfBounds in BigInteger class
 Description of Problem:
 Occasionally (very occasionally) I've received bug reports mentioning this
 showing up in Visual Studio when running monotorrent:
@@ -455,6 +454,35 @@
 	bi.data = t;  <<<< HERE
 I think this code is not thread safe, bi is shared and it is modified
 by each thread.
+------- Additional Comments From sebastien at ximian.com  2007-08-13 14:10 -------
+Not sure if we're all understanding each other... :(
+> Which indicates that the problem is in BigInteger class. 
+Yes, the problem occurs inside BigInteger class. But the question
+wasn't where but why ;-)
+> I also recompiled the test sample with csc and I got same exception.
+Alan's problem occurred only when Mono.Security.dll was compiled by
+MCS, not when it was compiled by CSC. Still true Alan ?
+If so then it has nothing to do with compiling the test sample.
+> I think this code is not thread safe,
+No it's not - and wasn't mean to be.
+> bi is shared and it is modified by each thread.
+Yes in the first sample but in the second sample there is no shared
+Alan can you confirm the problem was occuring with the second sample ?
+(and only when MCS was used to compile Mono.Security.dll ?)

More information about the mono-bugs mailing list