🚀 go-pugleaf

pharr-matthew@CS.YALE.EDU (Matthew Pharr) writes:
>If I remember correctly, a fair number of Unix systems -aren't-
>crashed by CrashMe.  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

Well not exactly (UNIX systems protect memory properly).
From the man page...

DESCRIPTION
     crashme is a very simple program that tests the operating
     environment's robustness by invoking random data as if it
     were a procedure.  The standard signals are caught and han-
     dled with a setjmp back to a loop which will try again to
     produce a fault by executing random data.
-- 
Andy Newman (andy@research.canon.oz.au)		"int - God's own type"