Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 328959

Summary: PTP Remote C project make does not show output when build fails
Product: [Tools] PTP Reporter: Chris Genly <genly>
Component: RDTAssignee: Project Inbox <ptp-inbox>
Status: CLOSED DUPLICATE QA Contact:
Severity: major    
Priority: P3 CC: recoskie
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard:

Description Chris Genly CLA 2010-10-28 14:21:12 EDT
Build Identifier: M20100909-800

I have a remote C project called a_remote in my Windows Eclipse.  The project data resides on a remote Linux machine called longhorn. I'm using Remote Tools for the remote C project.  The C project was created with the Remote C/C++ Project wizard.  I've added a makefile and a simple test source.  

If I have a source file with an error, and I build from Eclipse by pressing the build toolbar button, no output is shown in the build console or the problems view.

Here are some experiments I tried:

Starting with a good C source file. If I run the makefile from an RSE terminal connected to longhorn, the project will build.

If I then run the build by pressing the build button on the toolbar, the console shows "make: Nothing to be done for 'all'."

If I delete the executable a_remote/Debug/a_mpi_test and press the build button I see:
"mpicc -o Debug/a_mpi_test Debug/a_mpi_test.o"

If I delete the executable, a_remote/Debug/a_mpi_test, and the object, a_remote/Debug/a_mpi_test.o the build by pressing the build button I get nothing in the console, but the build completes (I can see the object and executable appear).  An error appears in the Error view.

If I put a syntax error in the C source file, and press build, I get nothing in the console or problems view.  An error does appear in the Error view.


java.lang.NullPointerException
	at org.eclipse.cdt.make.internal.core.scannerconfig.gnu.GCCPerFileBOPConsoleParser.processCommand(GCCPerFileBOPConsoleParser.java:124)
	at org.eclipse.cdt.make.internal.core.scannerconfig.gnu.AbstractGCCBOPConsoleParser.processSingleLine(AbstractGCCBOPConsoleParser.java:300)
	at org.eclipse.cdt.make.internal.core.scannerconfig.gnu.AbstractGCCBOPConsoleParser.processLine(AbstractGCCBOPConsoleParser.java:141)
	at org.eclipse.cdt.internal.core.ConsoleOutputSniffer.processLine(ConsoleOutputSniffer.java:181)
	at org.eclipse.cdt.internal.core.ConsoleOutputSniffer.access$0(ConsoleOutputSniffer.java:179)
	at org.eclipse.cdt.internal.core.ConsoleOutputSniffer$ConsoleOutputStream.checkLine(ConsoleOutputSniffer.java:109)
	at org.eclipse.cdt.internal.core.ConsoleOutputSniffer$ConsoleOutputStream.close(ConsoleOutputSniffer.java:77)
	at org.eclipse.ptp.rdt.core.remotemake.RemoteMakeBuilder.invokeMake(RemoteMakeBuilder.java:452)
	at org.eclipse.cdt.make.core.MakeBuilder.build(MakeBuilder.java:98)
	at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:629)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
	at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:172)
	at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:203)
	at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:255)

If you need more information, or if there is a way for me to collect more data, please let me know.


Reproducible: Always
Comment 1 Chris Recoskie CLA 2010-10-28 15:08:22 EDT

*** This bug has been marked as a duplicate of bug 316359 ***