[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [csmith-dev] gcc crash and csmith bug
I guess a trivial way to get the best of both worlds is to flush the
output right after the boilerplate header text, but make sure that the
last line of that header text is something like
/* CAUTION: If this comment is the last thing in this file, that means
Csmith crashed or was killed
I think this is a reasonable idea.
Thanks for noticing what was going on, Arthur!
Of course SIGKILL cannot be caught. Perhaps there's a way to get ulimit
to instead send SIGTERM?
The non-portability of this kind of thing to Windows isn't a big problem
as far as I'm concerned.