-.d file created with Core Build Makefiles about cdt

[jonahgraham]

This appears to be a result of running the scanner with the collected command line arguments in the output of the build. i.e. CDT sees g++ -c -g -MP -MMD -o example24.o /scratch/eclipse/src/cdt/runtime-CDT/example24/example24.cpp and uses that to construct a command line to pass to g++ that contains the -MP -MMD which has the side effect of leaving the errant -.d file around.

This is an example of the command line:

/usr/bin/g++ -E -P -v -dD -c -g -MP -MMD -o - /scratch/eclipse/src/cdt/runtime-CDT/example24/.sc2298146184504750215.cpp

This is the relevant stacktrace that creates the above g++ process.

Daemon Thread [OutputReader] (Suspended (entry into method <init> in Process))	
	owns: ConsoleOutputSniffer  (id=17990)	
	ProcessImpl(Process).<init>() line: 96	
	ProcessImpl.<init>(byte[], byte[], int, byte[], int, byte[], int[], boolean, boolean) line: 338	
	ProcessImpl.start(String[], Map<String,String>, String, Redirect[], boolean) line: 271	
	ProcessBuilder.start(ProcessBuilder$Redirect[]) line: 1107	
	ProcessBuilder.start() line: 1071	
	GCCToolChain.getScannerInfo(IBuildConfiguration, List<String>, Path, Path) line: 465	
	GCCToolChain.getScannerInfo(IBuildConfiguration, List<String>, IExtendedScannerInfo, IResource, URI) line: 384	
	StandardBuildConfiguration(CBuildConfiguration).processLine(String) line: 834	
	ConsoleOutputSniffer.processLine(String) line: 180	
	ConsoleOutputSniffer$ConsoleOutputStream.checkLine(boolean) line: 101	
	ConsoleOutputSniffer$ConsoleOutputStream.write(byte[], int, int) line: 60	
	ConsoleOutputSniffer$ConsoleOutputStream(OutputStream).write(byte[]) line: 122	
	ProcessClosure$ReaderThread.run() line: 60	

[jonahgraham]

Thanks to @EonDigital for helping identify this issue.