[Mono-bugs] [Bug 77570][Nor] Changed - Segfault within the GC only
when using the debugger
bugzilla-daemon at bugzilla.ximian.com
bugzilla-daemon at bugzilla.ximian.com
Tue Apr 18 14:30:31 EDT 2006
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 martin at ximian.com.
http://bugzilla.ximian.com/show_bug.cgi?id=77570
--- shadow/77570 2006-02-15 18:34:09.000000000 -0500
+++ shadow/77570.tmp.12764 2006-04-18 14:30:31.000000000 -0400
@@ -1,14 +1,14 @@
Bug#: 77570
Product: Mono: Debugger
Version: 1.1
-OS:
+OS: unknown
OS Details:
-Status: NEW
-Resolution:
-Severity:
+Status: RESOLVED
+Resolution: FIXED
+Severity: Unknown
Priority: Normal
Component: cli
AssignedTo: martin at ximian.com
ReportedBy: joeshaw at novell.com
QAContact: mono-bugs at ximian.com
TargetMilestone: ---
@@ -88,6 +88,12 @@
/home/joe/cvs/beagle/tools/Settings.cs:44
I also tried with another program which shared some of the same code, and
the stack trace was essentially the same at the lowest frames. Both call
mono_array_new_specific() before going into the GC. With the other
program, I believe it was happening when constructing a Hashtable.
+
+------- Additional Comments From martin at ximian.com 2006-04-18 14:30 -------
+I fixed a related issue last week. We had a really bad GC-related bug
+in the debugger.
+
+Another way of reproducing this was running XSP in the debugger.
More information about the mono-bugs
mailing list