An internal error occurred during: "Searching for local changes".

Larry,

Just to make sure I understand the problem if you go to:

File -> New  -> New File, and then selecting advanced and "link to the file in the file system"

You hit a problem that it won't let you continue.

What happens if you right click on your project and select "Like Files to Project..."?  Does that give you the same error?

Regards,

John

Here is the error I'm seeing.  What does it mean?  How can I fix it?

I am deas in the water here!

By the way, linked files don't work either.  I dont get an error, but the .project file does not get updated and the file does not show up under the project

Larry,

Thanks for letting us know what the issue was.  Was the project under source control?  Curious what might have caused the corruption.

John

John,

I'm at a customer right now that is experiencing this exact same issue. If I create a new workspace I can keep working but as soon as I shut down the debugger and exit CCS things get corrupted again.

The OS is Windows 7 64-bit Professional. The CCS version is 4.1.3.00038. The device is TMS320F28035 (running the FlashingLeds demo).

I'm running Windows 7-64 bit Home Premium under VMWare Fusion with CCS 4.1.3.00038 on my MBP and am not experience this issue. The customer's Vista (32-bit) machine is also not having any issues.

Can we get this escalated to determine the root cause?

Thank you,

Tim

Tim,

If the project has gotten corrupted then creating a new workspace and importing the same project into it likely won't help.  For the ControlSuite examples when you import them the instructions are to leave them in their original location so importing that project into another workspace will mean the problem will be in the new workspace as well as it is still physically the same project.

One option would be to install a second copy of control suite and try importing the project again from that installation.

I can't see the problem myself using Win7 64 and the same example.  Could they export the project to an archive and attach it to the thread?  I could try importing it and see if I can see the problem using their project.

John

Tim,

It would also be helpful if they could send the Eclipse error log.  That can be exported by opening the Error Log View.

http://processors.wiki.ti.com/index.php/Troubleshooting_CCS#Eclipse_Error_Log

Regards,

John

John,

I had some time to do some testing on the customer's configuration. If the debugger is connected to the target and you click on the "Terminate All" icon in the tool bar it causes Java to crash. If you then proceed to exit out of CCS then restart it things are corrupted and it will not load the last workspace and/or project correctly. If I exit CCS, relaunch, and create a new workspace I can re-import the last active project without issue.

To workaround this issue and avoid the Java crash we are able to just exit CCS (without clicking on "Terminate All") directly. We can relaunch CCS without issue. I'm not sure what pieces of CCS are tied to Java but something is causing Java to crash when "Terminate All" is selected in the debugger.

I will try to send you the CCS log file tomorrow.

Tim

Tim,

Ok so they have a JVM (Java) crash and then after than the project is not usable in the workspace and they have to import into a different one.

We should try to get the JVM error logs as well.  They are a bit more tricky to find.  JVM error logs are generated somewhere inside '<INSTALL DIR>\ccsv4' folder. It is recommended to do a recursive search inside that directory for *.log files. JVM error logs will look something like 'hs_err_pid<some number>.log' (for example: hs_err_pid4044.log) ).  Hopefully we can figure out what is causing the crash.

Regards,

John

I'm seeing the same behaviour as Larry and Tim. Would you like to have my logs as well?

/Anders

Anders,

That would be great.  Thanks.

John

I am suddenly seeing this problem as well. 

Here are my error and JVM log files.  Nasty.

Hi, 

Could you let us know which version of CCS you are using, HW target and host OS? Do you get the crash when trying to terminate debug session, but not when closing CCS?

Thanks,
martin

This problem occurs on opening CCS.  I'm using CCS4.2.1.00004   on Win 7(64bit)  XDS100V2 emulator for C6745. 

I tried narrowing the source of the problem by deleting files and subsequently subfolders and then restoring them from subversion until the problem went away, but I was unsuccessful in this.  I was finally able to fix  the problem by deleting the entire project directory and restoring it, but I never found out what the real cause was. Perhaps a missing file????

I suddenly started having this problem too. I took the advice and went through all my projects and found the one that if closed, allowed the others to open successfully. Now to figure out whats wrong with the offending project.

I am seeing the same behavior --- using Terminate All results in the offending error next time CCS is started.

I have WinXP SP3, CCS 4.2.3.0004, SD XDS510 debugger.  To repair, I deleted the offending project, re-started CCS, and imported the same project.

me too: CCS Version: 4.2.4.00033