I am using CCS 5.1.0.09000. As soon as a .cpp source file is saved containing the keyword 'restrict', the C/C++ indexer starts, but it will never finish and causes 1 CPU to be loaded 100%.
Attempts to disable the indexer will fail as long as it is running, and cause the IDE to hang.
Attempts to cancel the indexer will cause the subsequent build atttempt to hang.
Both hangups can only be solved by killing CCS, removing the 'restrict' keyword from the source file (with an another editor) and start CCS again...
Is there a fix for this?
Regards,
Ruud Pendavingh
Ruud,
Would you mind sending a testcase that reproduces this issue? I used a simple code shown attached and the indexer runs fine.
I am using the same version as you on a Windows 7/64 bits.
Rafael
Hi Rafael,
I just created a new workspace containing a new project with your restrictTestcase.cpp. The indexer runs fine.
Switched back to my original workspace again, added the keyword 'restrict' to one of my source files: the indexer does NOT hang. It seems that I cannot reproduce the problem anymore ?!
Thanks so far!
Ruud
Thanks for reporting this; what we usually see is that sometimes the workspace appears to be "locked" in a specific state/behaviour and either changing workspaces or "cleaning" them (invoking ccstudio.exe -clean) turns back the expected behaviour.
Just FYI, some troubleshooting ideas are shown at:
http://processors.wiki.ti.com/index.php/Troubleshooting_CCSv5