[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:15: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 abockover at novell.com.
http://bugzilla.ximian.com/show_bug.cgi?id=80229
--- shadow/80229 2006-12-11 17:15:06.000000000 -0500
+++ shadow/80229.tmp.21121 2006-12-11 17:15:40.000000000 -0500
@@ -30,6 +30,11 @@
While the developer should always explicitly check for null before
dereferencing instead of relying on exceptions for flow control, a segfault
is quite bad. I found this after some code was introduced in Banshee that
did exactly that (rely on the exception), and I could no longer debug under
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
+
More information about the mono-bugs
mailing list