Eclipse 4 launcher produces segfault when provided launcher.openFile with relative-looking path

[utzeln]

Related to https://bugs.eclipse.org/bugs/show_bug.cgi?id=439459 .

For CSS, it is then no more possible to open from command line an OPI with relative path according to OPI Search Path preference.

Relative path within the workspace works - such as:

--launcher.openFile "/BOY Examples/main.opi macro1 = hello, macro2 = hello2,Position=Detached"

As well as full path on Linux.

[anzez]

Just one additional comment - as explained by Nadine, this works ok:
--launcher.openFile "/workspace/path/to/main.opi"
And so does:
--launcher.openFile "/absolute/file/system/path/to/main.opi"

However, this doesn't (segfaults):
--launcher.openFile "relative/path/to/main.opi"

This is the case for both OPI search paths as well as for (all relative) file system paths.

You also can't specify additional arguments after the --launcher.openFile, e.g.:
--launcher.openFile /path/to/opifile -clean
(eclipse will treat '-clean' as a relative path and effectively segfault)

[kasemir]

Good that you found the eclipse bug link, it's indeed a problem, and one that we can't easily fix.

On the other hand, good that it works fine with complete paths.
Do you really need that search path?
I've been avoiding it. We used it with EDM, but the result is that you never know which screen you might get. Better install your screens, or use soft links, or whatever else it takes so that your screen links can be complete paths (in the workspace) without relying on a search path.

[utzeln]

For us, it is not a showstopper - the full path is fine.