Bug 482596 - Provide a way to get access to Process.exitValue() in CommandLauncher
Summary: Provide a way to get access to Process.exitValue() in CommandLauncher
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-build (show other bugs)
Version: Next   Edit
Hardware: PC Windows NT
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: cdt-build-inbox@eclipse.org CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-19 09:44 EST by Andreas Muelder CLA
Modified: 2020-09-04 15:25 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas Muelder CLA 2015-11-19 09:44:40 EST 
There is no way to get the return code of an external process launched via the ExternalBuildRunner -> BuildRunnerHelper -> CommandLauncher.

The result of fProcess.waitFor() which indicates the process exit code is ignored. Instead, the CommandLauncher#waitAndRead returns a custom status code which can be either ILLEGAL_COMMAND, COMMAND_CANCELED or OK. 

Thus, even when the process terminates with an exit code != 0, the returned Status code is OK, this is not the correct behaviour.