• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 54 subscribers
  • Views 1654 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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: CCS crashes after any attempt to create new project (Linux CentOS-7)

Sergey Markov
Intellectual 510 points
Other Parts Discussed in Thread: CCSTUDIO

Tool/software: Code Composer Studio

CCS (versions 7.1.0.00016, and 7.3.0.00019) crashes after I select "File -> New -> Project", then I select any of project types (i.e. "CCS Project"), then I press "Next", then CCS crashes after two-three seconds after dialog with project parameters appears.

Console output:

[s-markov@localhost ~]$ /opt/ti71/ccsv7/eclipse/ccstudio

dvtLogOptions.xml DOES NOT exists
Aborted (core dumped)

Version of operating system:

[s-markov@localhost work2]$ rpm --query centos-release
centos-release-7-4.1708.el7.centos.x86_64
[s-markov@localhost work2]$ cat /etc/redhat-release
CentOS Linux release 7.4.1708 (Core)
[s-markov@localhost work2]$ uname -r
3.10.0-693.11.1.el7.x86_64

All of the latest updates applied to the operating system.

How to do?

  • 0
    TI__Guru**** 171299 points
    Hi,

    I am trying to set up CentOS 7 on a VM here but so far it has been collapsing for me at the first boot right after installing (can't mount /sysroot)

    As you mentioned the latest updates were applied to the OS, double check to see if glibc 2.26 was installed or not. CCSv7.3 and earlier have an incompatibility with this version of the library (already fixed in the upcoming CCSv7.4).

    e2e.ti.com/.../628971

    Regards,
    Rafael
  • 0 in reply to desouza
    Intellectual 510 points

    CentOS (as well as official RHEL) distributions are not using latest versions of  glibc and other critical libraries. Latest glibc from CentOS is 2.17 release 196.el7_4.2

  • 0 in reply to desouza
    Intellectual 510 points

    Some more info:

    I've "straced" CCS, and found this error message (not shown in console) before crash:

    ccstudio: /builddir/build/BUILD/oxygen-gtk2-1.3.4/src/animations/oxygencomboboxdata.cpp:87: void Oxygen::ComboBoxData::setButton(GtkWidget*): Assertion `!_button._widget' failed.

  • 0 in reply to desouza
    Intellectual 510 points

    I've found a workaround to fix this problem.

    This is general bug of KDE, not of CCS or eclipse - bugs.kde.org/show_bug.cgi

    way to fix:

    This seems to be a bug in GTK according to 

    (there a similar problem for Meld was reported).

    Another workaround mentioned there is

    For oxygen, edit the normally already existing file "/usr/share/themes/oxygen-gtk/gtk-2.0/gtkrc" and change

       GtkComboBox::appears-as-list = 1

    into

       GtkComboBox::appears-as-list = 0

  • 0 in reply to Sergey Markov
    TI__Guru**** 171299 points

    Sergey,

    Thank you very much for reporting back your findings. Since yesterday I have been trying to have a working setup of CentOS 7 on my VMware workstation but I couldn't get anywhere. 

    Regards,

    Rafael

  • 0 in reply to desouza
    Intellectual 510 points
    Main problem of troubleshooting CCS failures is that it's output to stderr are masked. I was able to see the error message only through the use of strace ( I found "write (2, "error_message_text")" syscall among several megabytes of strace's text output)) . If CCS did not mask the output of error (stderr) messages to the console, it would be much faster to find the source of the problem.
  • 0 in reply to Sergey Markov
    TI__Guru**** 171299 points
    Sergey,

    Sorry about the delay. Yesterday I filed the enhancement number CCDSK-3024 to send your request for consideration.

    Please check its status in about 1/2 hour at the link SDOWP in my signature below.

    Regards,
    Rafael
  • 0 in reply to desouza
    TI__Guru**** 171299 points
    Sergey,

    Eclipse already has the -debug command line option, which can be used with the -consoleLog option for tracking. However, it is not as comprehensive as strace or Windbg as it does not track OS and driver calls but it at least reports errors.

    Do you think this would be enough for this particular case? We are trying to be sure we can address this with the existing functionality.

    Regards,
    Rafael