[Mono-bugs] [Bug 81289][Nor] Changed - Unhandled System.ArgumentOutOfRangeException

[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 monkey at jpobst.com.

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

--- shadow/81289	2007-04-02 03:18:29.000000000 -0400
+++ shadow/81289.tmp.11032	2007-04-02 11:46:17.000000000 -0400
@@ -2,21 +2,20 @@
 Product: Mono: Class Libraries
 Version: 1.2
 OS: GNU/Linux [Other]
 OS Details: Gentoo (default-linux/x86/2006.1/desktop profile)
 Status: NEW   
 Resolution: 
-Severity: 
+Severity: Unknown
 Priority: Normal
 Component: Windows.Forms
 AssignedTo: toshok at ximian.com                            
 ReportedBy: lists at gnudental.org               
 QAContact: mono-bugs at ximian.com
 TargetMilestone: ---
 URL: 
-Cc: 
 Summary: Unhandled System.ArgumentOutOfRangeException
 
 Background:
 
 Open Dental(R) is a Windows(R) application with a 4-6 year history that is
 in production use now and is authored primarily by Jordan S. Sparks, DMD
@@ -223,6 +222,26 @@
 LINGUAS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
 
 ------- Additional Comments From lists at gnudental.org  2007-04-02 03:18 -------
 Created an attachment (id=18991)
 Patch commenting line in Open Dental(R) code which throws unhandled exception
 
+
+------- Additional Comments From monkey at jpobst.com  2007-04-02 11:46 -------
+Looking at your stacktrace:
+Unhandled Exception: System.ArgumentOutOfRangeException: Argument is
+out of range.
+Parameter name: startIndex
+  at System.String.Substring (Int32 startIndex) [0x00000] 
+  at OpenDental.ContrChart..ctor () [0x00000] 
+<snip>
+
+My guess would be that you are running on a culture that is not at
+least 4 letters long, so your:
+if (CultureInfo.CurrentCulture.Name.Substring (3) != "CA")
+is failing on the Substring.
+
+Maybe write CultureInfo.CurrentCulture.Name out to the console before
+this line on the affected system to see if it's long enough?
+
+If that doesn't do it, would it be possible to get a stacktrace using
+mono --debug so that line numbers are included?