Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!tinman.cis.ohio-state.edu!bob
From: bob@tinman.cis.ohio-state.edu (Bob Sutterfield)
Newsgroups: comp.sys.next
Subject: Re: X-11 and NeXT
Message-ID: <BOB.89Jul13091455@tinman.cis.ohio-state.edu>
Date: 13 Jul 89 13:14:55 GMT
References: <11681@cgl.ucsf.EDU> <7866@spool.cs.wisc.edu>
	<BOB.89Jul12120430@tinman.cis.ohio-state.edu>
	<12625@bloom-beacon.MIT.EDU>
Sender: news@tut.cis.ohio-state.edu
Reply-To: Bob Sutterfield <bob@cis.ohio-state.edu>
Organization: The Ohio State University Dept of Computer & Information Science
Lines: 6
In-reply-to: jfc@athena.mit.edu's message of 12 Jul 89 23:13:35 GMT

In article <12625@bloom-beacon.MIT.EDU> jfc@athena.mit.edu (John F Carr) writes:
   The NeXT has helped us catch a lot of NULL pointer dereferences in
   code we've tried to run on it...both Vax and RT have *(int *)0 == 0
   by default, but the NeXT has *(int *)0 == core dump.

Heck, even a Sun can do that - where's the nifty new NeXT technology? :-)