🚀 go-pugleaf

In article <1992Oct1.113425.27867@cs.yale.edu> pharr-matthew@CS.YALE.EDU  
(Matthew Pharr) writes:
> If I remember correctly, a fair number of Unix systems -aren't-
> crashed by CrashMe.  
Yes, I read SunOS 4.1.2 doesn't crash on sparcs. While 4.1.1 does.
> Anyway, what CrashMe does is fork as many
> processes as it can and write to memory randomly, in the hopes of
> destroying something important that the o/s wasn't protecting
> properly. I would assume that the problem NeXTs have with this is the
> same old one that comes up when you fork() too many processes or
> threads--the panic out of nowhere and lock-up that was discussed
> earlier in the thread about what happens when you try to write a
> multi-threaded app with, say, 200 threads...
> 
> matt
Wrong! Yes it forks, and each son writes random bytes to KNOWN location  
and then tries to execute this random code. BTW I hope (and believe) that  
040 is ok but the OS is wrong.

Frank