Chapter 3. Known Issues in Eclipse 4.7.0

Cause: When a user attempts to install a debuginfo package for this collection, for example: rh-eclipse47-eclipse-cdt-debuginfo, the contents may conflict with the same packages from the earlier collections.

Consequence: The installation of the rh-eclipse47 debuginfo package may fail if the same debuginfo package from the rh-eclipse46 collection is installed.

Workaround: To use debuginfo for the rh-eclipse47 collection, debuginfo packages from the rh-eclipse46 collection should first be uninstalled using the command yum remove rh-eclipse46*debuginfo.

Result: The installation of the debuginfo packages from the rh-eclipse47 collection is successful.

Cause: The rh-eclipse47-tycho package conflicts with the same package from the earlier collections, for example: rh-eclipse46-tycho.

Consequence: The installation of rh-eclipse47-tycho package may fail when rh-eclipse46-tycho package is already installed.

Workaround: Note that tycho is only needed by users who want to build or re-build Eclipse or its plug-ins. If needed, the rh-eclipse46-tycho package should be uninstalled using the command yum remove rh-eclipse46-tycho before attempting to install the rh-eclipse47-tycho package.

Result: The installation of the rh-eclipse47-tycho package is successful.

Cause: An enhancement to the BFD library in RHEL 7.4 broke the code that parses debug information.

Consquence: This is known to affect the gprof and perf components of the rh-eclipse47-eclipse-linuxtools package by causing Eclipse to fail to attribute samples to the correct source.

Workaround: This problem is fixed in the base RHEL binutils package via a separate erratum. Erratum RHBA-2017:2577 should be installed to fix this problem.

Result: After erratum RHBA-2017:2577 is installed, the gprof and perf tooling within Eclipse starts working as expected.

Cause: rh-eclipse47 provides support for running systemtap scripts. When the devtoolset-6-systemtap package is present, it takes precedence over the systemtap package present in the base operating system. However, when on RHEL 7.4, the devtoolset-6-systemtap package incorrectly uses a subset of runtime files of the base operating system systemtap and fails to run properly.

Consequence: The output of the scripts may contain errors and warnings indicating that wrong systemtap runtime files were used.

Workaround: When using the systemtap package on RHEL 7.4, the devtoolset-6-systemtap package should be uninstalled using the command yum erase 'devtoolset-6-systemtap*'.

Result: rh-eclipse47 will then use the systemtap package present in the base operating system which works with rh-eclipse47 without known issues.