> Actually clang doesn't need fork for error reporting at all. > The process can live on without problems even after the crash. > Here is what clang should do: Makes sense but what if some important bits (say argv) are trashed by stack overflow? -Y