Re: ccache interrupt handling bug

"Nadav Har'El" <[email protected]> writes:
> On Mon, Aug 17, 2015 at 12:50 AM, Tom Lane <[email protected]> wrote:
>> * make launches "ccache gcc -o test.o test.c"
>> * user types control-C
>> * ccache receives SIGINT and exits
>> * make does unlink("test.o") to clean up after failed compile step, which
>> it thinks is done
>> * gcc creates test.o

> Stupid question: Does ccache let gcc write to test.o directly, or does it
> write to some temporary file and then ccache copies it?

Dunno, but that just moves the problem somewhere else no?  For instance,
in the code fragment you mentioned, I wonder whether it's sane to do
"clean_up_pending_tmp_files();" when gcc is still on the loose.

			regards, tom lane