If an application starter executable will be executed with an unrecognized (not consumed, handled) command line option, a RCP suite terminates. This is ok, but the user must have a feedback. On the desktop, the executable will be started usually via a link (shortcut, desktop icon) and that link can contain the user specific command line option.
From the user's point of view, a click on the desktop icon shows the splash screen for a while and then it disappears, the application does not run. Even the log file does not contain any message with the cause. Only if executed in a console (command line, DOS Box), the behaviour cause is visible - e.g. if started with "myapp.exe --not_consumed_cmd_option" - the console shows the cause - but it's not ok at all, because every command line program I know then displays all aviable command line options and their description.
The executable builder should be extended to display a dialog box with a message e.g. "The command line parameter --bla is not valid" (or the RCP should do that).