• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 54 subscribers
  • Views 351 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 V6 - ccstudio crashed with SIGSEV in GetHomeDir()

Daniel Matthes
Prodigy 20 points
Other Parts Discussed in Thread: CCSTUDIO

I have a problem with the currently version of CCS. At first I have installed it on Ubuntu 14.04 without problems. When I'm logged in as a local user everything works find. I can start CCS V6 and use it without problems. So far, so good.


Now my Problem:
We also have installed winbind on our PCs, in order that the students of our institute can use their Active Directory Accounts for login. Using this account CCS V6 will not start. During the start up ccstudio crashs with the following error message: "ccstudio crashed with SIGSGV in GetHomeDir()". I have also used strace to get some further informations. It seems that ccstudio will access to the i386 version of libnss_winbind.so.2, but the library isn't found. (my system is a 64 bit system) Therefore I had the idea to install the i386 version of the mentioned library, but that didn't work there are too munch forbidden dependencies.

I have now no further ideas to solve this problem and I wonder that this problem in CCS V5 doesn't appear. May you help me!

Best regards Daniel

  • 0
    TI__Guru**** 472431 points

    Daniel Matthes said:
    It seems that ccstudio will access to the i386 version of libnss_winbind.so.2, but the library isn't found. (my system is a 64 bit system)

    Since CCS itself is a 32-bit application, it makes sense that you would need the 32-bit version of the library.

    Daniel Matthes said:
    Therefore I had the idea to install the i386 version of the mentioned library, but that didn't work there are too munch forbidden dependencies.

    What are the other dependencies?

    Daniel Matthes said:
    I have now no further ideas to solve this problem and I wonder that this problem in CCS V5 doesn't appear

    CCSv5 is also a 32-bit application so I would imagine you would run into the same issue. You would need a way to install all the dependencies for the 32-bit version of needed libraries.

  • 0 in reply to Ki
    Prodigy 20 points

    Ki-Soo Lee said:
    What are the other dependencies?

    If I want to install libnss-winbind:i386, I also have to install winbind:i386, samba:i386 and python:i386 too. That's not possible, because this will lead to the removal of the 64-bit versions of theses tools and in addition of a huge amount of other dependent programs.

    Ki-Soo Lee said:
    CCSv5 is also a 32-bit application so I would imagine you would run into the same issue.

    Definitely not. I have tested it today. I have reinstalled version 5.5 beside version 6 and I can use it without this problem. Unfourtunately version 5.5 has other bugs (for example the JTAG programmer crashs casual), which are fixed in version 6. So version 5.5 is  no option for me.

    I have attached my strace output. Maybe this would lead you to a solution.


    Best regards

  • 0 in reply to Daniel Matthes
    TI__Guru**** 472431 points

    Thank you for attaching the strace output. The engineers took a look but unfortunately they don't have a solution. There are some dependencies that simply cannot be resolved. It is a mismatch of the 64-bit app and 32-bit CCS. Not sure why v5 is working but v6 is not since they are both 32-bit and use the same version JRE. Perhaps it is the Eclipse version.

    Daniel Matthes said:
    Unfourtunately version 5.5 has other bugs (for example the JTAG programmer crashs casual), which are fixed in version 6. So version 5.5 is  no option for me.

    You can try updating the emu pack that comes with 5.5. Try running the Update Manager to look for new updates and see if there is a TI Emulator update. It may have a fix for your JTAG issue.

    Sorry we could not be more help.

    ki