• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 52 subscribers
  • Views 1263 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 fails to start due to a stack overflow error

Gennadiy Kiryukhin
Expert 2800 points

Tool/software: Code Composer Studio

I have two project that I have added a cross-reference to under advanced settings and it caused a stack overflow error preventing CCS from starting up.

To recreate, create two projects in CCS, and for both projects, go to Properties, click Show advanced setting, under Project References, select the other project to create the cross-reference.

I was able to recover by opening  .cproject file in notepad and manually removing the reference (just searched for the other projects name to find it).

  • 0
    TI__Guru**** 173310 points

    Gennadiy Kiryukhin said:
    To recreate, create two projects in CCS, and for both projects, go to Properties, click Show advanced setting, under Project References, select the other project to create the cross-reference.

    Did you intend to create the cross-reference for both projects or was it done unintentionally? Typically you only want to create the reference one -way, (ie) the main/application project references a library project. I don't know why but Eclipse seems to allow Project References both ways that then results in the stack overflow error. However, the CCS version of that setting (Project Properties->Build->Dependencies tab) prevents you from creating references both ways. For CCS projects, we recommend using Dependencies which only allows one-way dependencies. 

  • 0 in reply to AartiG
    Expert 2800 points

    I have two projects that are related, reside in different flash sectors and can call each other. Adding references was an "exploratory" step to see if it could simplify running debugger for both projects in one session.

    If a user should not use Project References in CCS, then this option/setting should be removed as it creates a potential for somebody to brick their CCS requiring manual editing of project xml files.

  • 0 in reply to Gennadiy Kiryukhin
    TI__Guru**** 173310 points

    Gennadiy Kiryukhin said:
    I have two projects that are related, reside in different flash sectors and can call each other.

    This use-case does not require creating references.

    References (or dependencies) are more of a build setting to tell the managed build system that a referenced project should be built before the main project that references it is built.

    I understand that your intention was to explore and experiment with the setting and I agree that a stack overflow error and subsequent breaking of project should never happen. However since this is an Eclipse component I'm not sure if it is something TI can fix. Nevertheless I have filed the issue so the developers can investigate it. The tracking ID is CCSIDE-3671. 

    Thank you for bringing this to our attention.