This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCS/CCSTUDIO: CCS V5 Sporadic Crash with "libgtk-x11-2.0.so.0" on 64bits CentOS 7

Part Number: CCSTUDIO

Tool/software: Code Composer Studio

When I try to use CCS function, e.g. Create a new project by "Makefile from exsiting code", the CCS crashed as below:

$ ./ccstudio 

(ccstudio:12609): Gtk-WARNING **: 03:52:59.877: Unable to locate theme engine in module_path: "adwaita",

(ccstudio:12609): Gtk-WARNING **: 03:52:59.909: Unable to locate theme engine in module_path: "adwaita",
Gtk-Message: 03:52:59.911: Failed to load module "pk-gtk-module"
flxInitLoad: client has not been protected.
#
# An unexpected error has been detected by Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0xf6257af5, pid=12609, tid=4149077760
#
# Java VM: Java HotSpot(TM) Client VM (11.3-b02 mixed mode linux-x86)
# Problematic frame:
# C  [libgtk-x11-2.0.so.0+0x273af5]
#
# An error report file with more information is saved as:
# /tmp/hs_err_pid12609.log
#
# If you would like to submit a bug report, please visit:
#   java.sun.com/.../crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.

I have followed the guide for 64bits Linux: http://processors.wiki.ti.com/index.php/Linux_Host_Support_CCSv5#Fedora_20_64bit. I have to use this version CCS 5.5, because I cannot migrate Simulator to CCS9. 

I do not understand what's wrong with the GTK, Is the version problem? or memory too small? or because I installed both gtk X86_64 & i686 lib??? When I run check_depends.sh, I have been notified:

[root@localhost work]# ./check_depends.sh
Installed versions of glibc and glibcxx: __xstat64@GLIBC_2.1, N/A
Required versions of glibc and glibcxx: __xstat@@GLIBC_2.0, _ZTVSt9exception@@GLIBCXX_3.4
WARNING: A more recent GLIBC version is needed to run CCS.__xstat64@GLIBC_2.1 != __xstat@@GLIBC_2.0
Checking availability of libraries in ext-depends.txt ...
Done.

How should do to solve this CCS crash?

  • Hi,

    The combination of OS and CCS was never tested by us, but obviously that does not mean it wouldn't work. However, given the error happens sporadically, which makes debugging incredibly difficult, and the dependency checker throws a warning, I tend to act conservatively and suggest you to use one of the versions reported on the page you linked above.

    The relationship between Fedora 20 and CentOS 7 component versions is a bit convoluted, but there is a possibility the latter uses older components such as the one above. At any rate, I created a VM with a fresh CentOS 7 with all the components updated and I applied the dependencies you linked above and the ones for CCSv6 and CentOS 7 below:

    processors.wiki.ti.com/.../Linux_Host_Support_CCSv6

    Unfortunately I couldn't run the software - it failed with issues on libcairo.so. Perhaps the JVM used by CCSv5.5 is incompatible with the OS libraries.

    In the same system I installed CCSv6.1.3 (which still uses 32-bit libraries) and it worked flawlessly.

    At this point that is the extent of what we can do - given that CCSv5.5 is not supported anymore, there is a very little additional actions on my part. Sorry.

    Regards,
    Rafael
  • Rafael,

    Really thanks for help and trial. In fact, the crash is not sporadic, and the crash definitely happens at creating a new project by "Makefile from existing code" with above error.

    I understand V5.5 is quite old, and CentOS 7 may have difference with Fedora 20. I also ran into the " libcairo.so" issue when I configured "-Dorg.eclipse.swt.internal.gtk.cairoGraphics=false", but I can not get that error now whether I have mentioned configuration or not.

    As I talked before, CCS 5.5 is not my only or necessary choice, as long as I can run simulator. I seems that simulator can be migrated to higher CCS version, but I did not manage to do it for CCS 9, and I got "wrong ELF class: ELFCLASS32" error. Is that simulator can only migrate to 32 bits CCS other than 64 bits(e.g. CCS 9)?

    If so, 32 bits CCS choice could be CCS 6.1.3, which also was proved by you it works fine with CentOS 7. So my thought is if CCS5.5 is hard to fix, I can use CCS 6.1.3 with migrated simulator.
  • Hi,

    I set the same flag in ccstudio.ini on my v5.5 and CCS was able to open fine. However, the moment I tried to create a project, I hit the same issue as you.

    I was able to successfully create a project in CCSv6.1.3.

    Regards,
    Rafael
  • Thanks Rafael,

    I will try to install 32 bit CCSv6.1.3, and then migrate simulator to it.