[Mono-bugs] [Bug 80229][Nor] Changed - Segfault in gdb when trying to dereference a null System.Xml.XmlNode object
bugzilla-daemon at bugzilla.ximian.com
bugzilla-daemon at bugzilla.ximian.com
Mon Dec 11 17:52:40 EST 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 miguel at ximian.com.
http://bugzilla.ximian.com/show_bug.cgi?id=80229
--- shadow/80229 2006-12-11 17:15:40.000000000 -0500
+++ shadow/80229.tmp.21917 2006-12-11 17:52:40.000000000 -0500
@@ -1,14 +1,14 @@
Bug#: 80229
Product: Mono: Runtime
Version: 1.2
-OS:
+OS: unknown
OS Details:
-Status: NEW
-Resolution:
-Severity:
+Status: RESOLVED
+Resolution: NOTABUG
+Severity: Unknown
Priority: Normal
Component: misc
AssignedTo: atsushi at ximian.com
ReportedBy: abockover at novell.com
QAContact: mono-bugs at ximian.com
TargetMilestone: ---
@@ -35,6 +35,16 @@
gdb as Banshee would always segfault on startup.
------- Additional Comments From abockover at novell.com 2006-12-11 17:15 -------
Created an attachment (id=18277)
Test case exhibiting the segfault in gdb on null dereference of XmlNode
+
+------- Additional Comments From miguel at ximian.com 2006-12-11 17:52 -------
+segfaults are converted by the runtime to NullReferenceExceptions.
+
+If you do not want to see that in GDB, you need to use the standard:
+handle SIGSEGV pass noprint
+
+command.
+
+This is not a Mono bug.
More information about the mono-bugs
mailing list