[Mono-bugs] [Bug 48283][Wis] Changed - crash while running corlib unit tests

[bugzilla-daemon@bugzilla.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 vargaz@freemail.hu.

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

--- shadow/48283	2003-09-09 02:21:03.000000000 -0400
+++ shadow/48283.tmp.10673	2003-09-09 07:23:13.000000000 -0400
@@ -1,14 +1,14 @@
 Bug#: 48283
 Product: Mono/Runtime
 Version: unspecified
 OS: GNU/Linux [Other]
 OS Details: Debian unstable
-Status: NEW   
-Resolution: 
-Severity: 
+Status: RESOLVED   
+Resolution: NOTABUG
+Severity: Unknown
 Priority: Wishlist
 Component: misc
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: mass@akuma.org               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
@@ -109,6 +109,15 @@
 0x8d3ec7d:      call   0x400a942a <mono_array_new_specific>
 0x8d3ec82:      add    $0x8,%esp
 0x8d3ec85:      mov    %eax,%esi
 0x8d3ec87:      mov    %esi,0xfffffff0(%ebp)
 (gdb) print *(int*)($ebp + 0x8)
 $1 = 0
+
+------- Additional Comments From vargaz@freemail.hu  2003-09-09 07:23 -------
+This is not really a bug. The runtime does no checks for null pointers
+etc. Instead, it lets the hardware emit a SIGSEGV, then converts it
+into a NullReferenceException in the signal handler. Unfortunately, 
+gdb thinks it is a segmentation fault, confusing people.
+
+BTW, some Array methods threw NullReferenceException when they
+shouldn't. I fixed this.