🚀 go-pugleaf

In article <1992Oct1.113425.27867@cs.yale.edu> pharr-matthew@CS.YALE.EDU (Matthew Pharr) writes:

>>
>>So what.  Almost every Unix system is crashed in < 2 seconds by Crashme.
>>
>
>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.

This isn't what CRASHME is trying to do.  It forks a bunch 'o
processes, and causes each of them to execute randomly created
instructions.  It's really testing the exception handling ability of
the operating system, not the processor.

A properly working operating system should not crash and burn due to
stupid behavior of USER programs, which is what CRASHME is.  And there
are, as I recall, operating systems that don't die when you run
CRASHME.  One can argue that operating systems should behave
gracefully in the face of resource consumption (processes, VM, etc),
but I don't believe that CRASHME is attempting to provoke this sort of
problem.

This is also one of the class of problems/bugs that you might not even
waste your time reporting to NeXT.  They will be less interested in
this than they are of the real problems they need to fix.

	"It hurts when I do that."

	"Don't do that."

louie