[Mono-bugs] [Bug 46612][Nor] New - Segmentation fault on self-referencing property

[bugzilla-daemon@rocky.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 sebastian.nowozin@web.de.

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

--- shadow/46612	Sat Jul 19 08:15:07 2003
+++ shadow/46612.tmp.28792	Sat Jul 19 08:15:07 2003
@@ -0,0 +1,57 @@
+Bug#: 46612
+Product: Mono/Runtime
+Version: unspecified
+OS: 
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Normal
+Component: misc
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: sebastian.nowozin@web.de               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: Segmentation fault on self-referencing property
+
+Description of Problem:
+
+Upon (nonsense, but likely mistyped) constructs such as
+
+    public int Foobar {
+        get {
+             return (Foobar);
+        }
+    }
+
+mono crashes with a Segmentation fault. (Possibly stack internal overrun?)
+
+Steps to reproduce the problem:
+1. Compile the attached monocrash.cs with "mcs monocrash.cs"
+2. mono ./monocrash.exe
+
+
+Actual Results:
+
+Segmentation fault.
+
+
+Expected Results:
+
+Either an error message by mono, that the stack was overrun, or an endless
+looping.
+
+
+How often does this happen? 
+
+Reproducable.
+
+
+Additional Information:
+
+Maybe mcs could catch this mistake. (I suspect it may be a not-so-uncommon
+mistake, as people use lowercased names for their variables and uppercase
+for their properties, so a mistyping is common). At least, mono should not
+segfault.