Re: [csmith-dev] gcc crash and csmith bug

[Eric Eide <eeide@cs.utah.edu>]

	Arthur> John, etc.: I suggest that csmith not print *any* output until
	Arthur> it's ready to print *all* its output. That way, if it's killed
	Arthur> by ulimit, it won't leave a partial file behind.

Hmm.  One of my to-do's is to flush the output right after the header comment,
to make it easier for people to report bugs that we can reproduce.  That way,
if Csmith crashes, the identifying info is persisted.

But I can see the value of no output, too.  Something to ponder.

	Arthur> Alternatively, I don't know if this is possible, but depending
	Arthur> on how considerate ulimit is, maybe csmith should catch SIGKILL
	Arthur> (or whatever the signal sent by ulimit is)

While clever, that strategy is not directly portable to Windows.
Also something to ponder.

Eric.

-- 
-------------------------------------------------------------------------------
Eric Eide <eeide@cs.utah.edu>  .         University of Utah School of Computing
http://www.cs.utah.edu/~eeide/ . +1 (801) 585-5512 voice, +1 (801) 581-5843 FAX