[Mono-bugs] [Bug 52399][Min] Changed - StackOverflow in Type.GetType(name) with custom TypeResolve
bugzilla-daemon@bugzilla.ximian.com
bugzilla-daemon@bugzilla.ximian.com
Sat, 20 Dec 2003 14:38:04 -0500 (EST)
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 bmaurer@users.sf.net.
http://bugzilla.ximian.com/show_bug.cgi?id=52399
--- shadow/52399 2003-12-20 13:55:31.000000000 -0500
+++ shadow/52399.tmp.18058 2003-12-20 14:38:04.000000000 -0500
@@ -3,21 +3,21 @@
Version: unspecified
OS: unknown
OS Details:
Status: NEW
Resolution:
Severity: Unknown
-Priority: Critical
+Priority: Minor
Component: CORLIB
AssignedTo: mono-bugs@ximian.com
ReportedBy: tiago.lima@vianw.pt
QAContact: mono-bugs@ximian.com
TargetMilestone: ---
URL:
Cc:
-Summary: Two in one: StackOverflow in Type.GetType(name)
+Summary: StackOverflow in Type.GetType(name) with custom TypeResolve
Please fill in this template when reporting a bug, unless you know what you are
doing.
Description of Problem: Type.GetType(string name) gives a Segmentation fault
caused by a StackOverflow when an assembly is dinamicaly loaded.
@@ -42,6 +42,36 @@
Additional Information:
------- Additional Comments From tiago.lima@vianw.pt 2003-12-20 13:53 -------
Created an attachment (id=6286)
Loader.cs
+
+------- Additional Comments From bmaurer@users.sf.net 2003-12-20 14:38 -------
+Repro'd this on Windows, it works fine.
+
+Not critical at all however. Note the guidelines from Bugzilla:
+
+Critical
+ We should fix and push an update immediately. This will mostly be
+used for security fixes.
+Blocker
+ crashes, loss of data, severe memory leak
+Major
+ A major part of the component is nonfunctional.
+Normal
+ A minor part of the component is nonfunctional.
+Minor
+ The component mostly works, but causes some irritation to users. A
+workaround should usually exist.
+Cosmetic
+ The component works with 100% functionality, but has visible
+typos, etc.
+Wishlist
+ Generally a feature request for functionality the program doesn't
+already have. These can be useful as guides for future product
+improvements.
+
+This falls under the `minor' category (the workaround is pretty clear,
+it is not a common usage pattern).
+
+Thanks for reporting the bug, we do appreciate the help!