[Mono-bugs] [Bug 60330][Wis] New - change the content of a string property from inside the class causes a stack overflow

[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 raf@ophion.org.

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

--- shadow/60330	2004-06-17 02:01:01.000000000 -0400
+++ shadow/60330.tmp.8877	2004-06-17 02:01:01.000000000 -0400
@@ -0,0 +1,82 @@
+Bug#: 60330
+Product: Mono: Runtime
+Version: unspecified
+OS: 
+OS Details: FC2
+Status: NEW   
+Resolution: 
+Severity: Unknown
+Priority: Wishlist
+Component: misc
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: raf@ophion.org               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: change the content of a string property from inside the class causes a stack overflow
+
+Please fill in this template when reporting a bug, unless you know what you
+are doing.
+Description of Problem:
+
+
+Steps to reproduce the problem:
+1. Create a string property
+2. set its content from inside the class
+3. run the app
+
+Actual Results:
+
+What you see is a Unhandled Exception: System.StackOverflowException: The
+requested operation caused a stack overflow.
+and a long dump of something like this:
+
+in <0x00000> T:set_Blah (string)
+in <0x0000a> T:set_Blah (string)
+in <0x0000a> T:set_Blah (string)
+in <0x0000a> T:set_Blah (string)
+in <0x0000a> T:set_Blah (string)
+....
+
+
+
+Expected Results:
+
+The property should just be set
+
+How often does this happen? 
+
+All the time
+
+Additional Information:
+
+[raferrei@localhost tmp]$ mono --version
+Mono JIT compiler version 0.95, (C) 2002-2004 Novell, Inc and Contributors.
+www.go-mono.com
+        TLS:           NPTL
+        GC:            Included Boehm (with typed GC)
+        SIGSEGV      : altstack
+        Globalization: ICU
+[raferrei@localhost tmp]$
+
+I also had someone test on the IRC using a newer version of mono, and they
+were able to reproduce the problem.
+
+Here's an attached sample class that causes the error.
+
+using System; 
+
+class T {
+	public static string Blah {
+		get { return (Blah);}
+		set { Blah = value;}
+	}
+	
+	public static void Main()
+	{
+		Blah = "this is a test";
+		Console.WriteLine(Blah);	
+	
+	}
+}