The problem is that the version of the install.sh script, which is delivered with SDK 0.5, doesn't check for the presence of the GTK part of the consolehelper utility - /usr/bin/consolehelper-gtk. If this utility is not installed prior to running the script (which on RHEL 6.x is not present by default), the script will find /usr/bin/consolehelper and assume that consolehelper-gtk is installed and usable.
When you go to actually try OProfile, it will likely not work correctly, and you'll get an error dialog stating that you should try to run install-noconsolehelper.sh instead. If you do run that script at this point, it will overwrite the /usr/bin/consolehelper executable, due to a soft link from /usr/bin/consolehelper to opcontrol that was created by install.sh. This is quite bad, because the /usr/bin/consolehelper executable is then no longer usable.
To rectify this situation, do the following:
su root yum reinstall usermode yum install usermode-gtk cd /opt/ibm/ibm-sdk-lop/plugins/org.eclipse.linuxtools.oprofile.core* cd natives/linux/scripts rm opcontrol sh ./install.sh
Note that these problems will be fixed in subsequent releases of the SDK.