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: Crash & not start during splash screen

Expert 1965 points
Other Parts Discussed in Thread: CCSTUDIO

Tool/software: Code Composer Studio

After a clean install of CCS 9 (latest) on my Linux, it first started ok.

Then, after it pulled updates, CCS said needs to re-launch. After that, I cannot get pass the splash screen, it keeps crashing / getting killed, on some internal segfault. 
Tried cleaning all local user ti files, configs, workspaces - nothing.

Worth noting: because this is a 'sudo' type install  (effectively as root), this happens for the root user, which you have to use to upgrade / update, and install plugins.

For some strange reason, this error does not appear to manifest or to the same extent, as a 'normal' user - the CCS IDE starts if non-root user starts it.

However, it is still broken now for me as far as I cannot then update / install new plugins , as I need root...

No clue what is going on.. Anyone ?

So far it's been not best experience .. many segfaults errors and crashes while trying to access different parts / functions of CCS

  • I don't know if this trace can help, most likely not, but this is last thing i see when ltrace'ing the ccstudio binary.

    <snip..>

    strcat("", "localhost,,127.0.0.0/8,127.0.0.1"...) = "localhost,,127.0.0.0/8,127.0.0.1"...
    strstr("localhost,,127.0.0.0/8,127.0.0.1"..., "127.0.0.0/8") = "127.0.0.0/8,127.0.0.1/8"
    strstr("localhost,,127.0.0.0/8,127.0.0.1"..., "127.0.0.1/8") = "127.0.0.1/8"
    setenv("no_proxy", "localhost,,127.0.0.0/8,127.0.0.1"..., 1) = 0
    --- SIGSEGV (Segmentation fault) ---
    --- SIGSEGV (Segmentation fault) ---
    --- SIGSEGV (Segmentation fault) ---
    --- SIGSEGV (Segmentation fault) ---
    +++ killed by SIGSEGV +++

    bang, spash is gone .. app killed

  • I had to nuke that install, and restart.  

    When I re-started the installation binary, pointing to the same installation directory where previous version was installed, the installer told me something  along the lines , contains previous installation which is "corrupt"  . 

    So, could that be that the updates that are pushed to the CCS are corrupting Linux install .. ?

    After I've re-installed, at least I got back to things working. I do not know what was the original issue, and if it will/not come back again...

    (On the side note, default installation file creates few issues. Mostly ones I seen are incorrect / invalid permissions set on files - anything from no executable bits set on *.so files, to executable bits set on normal / plain files, to exec bits set on jars, etc . .. Some directories not executable (cannot change into) by non-owner, etc...

    Could be install was created based on Windows files/filesystem..  Also, some SDK packages I've seen get downloaded/installed, and create folders with full read/write access to folders to anyone, in user directory..  This is a bit of a hole for Linux.

    Anyone else saw this .. ?  I do not trust really that CCS Linux installer )