• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 53 subscribers
  • Views 923 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 5.1 project compile include paths are stuck

mes
Intellectual 530 points

Hi, I'm new to CCS5.1 from CCS3.3 and am having trouble with a new executable project I created in 5.1 from scratch.  My CCS version is:

 Version: 5.1.0.201108111000
 Build id: N201108111000

The problem is that, in the beginning, I was able to add, subtract, and change include paths under the C6000 compiler include options in the project properties.  Then it began acting strange.  It would not let me change them.   I could go into the include dialog, change/delete/add something, the change was reflected in the window, hit 'ok', but when you open it again, the changes have not been applied and it goes back to whatever it was previously.  

First there is a pop up that says "Operation In Progress...", and then for like a femto-second, a window with a red 'x' pops up with something about a 'An error ...' and 'nullPointer' - not long enough to actually read (i've tried several times).   When you go back to properties, the changes did not take effect.   I found a log with lots of errors which may give a clue that seem to be related.  Here is the recurring line:

"Problems occurred when invoking code from plug-in: "org.eclipse.jface"."

Including event information below:

The strange thing about the behavior is that it did not do this in the beginning.   I can make other changes to the project ok, like adding source or .cmd files.

Now that I try it, other areas of the properties dialog are not writable either.  For instance, I checked the box under Assembler Options to keep the generated assembly, hit ok, and that did not stick either.  Selecting Release or Debug configuration does not matter.

I'm starting over with the project today, making better initial estimates at the include files, but I think it will probably happen again. Any ideas?

Thanks,
Matt

 

this is from the event dialog found in the error log view:

eclipse.buildId=M20110909-1335
java.version=1.6.0_26
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Framework arguments:  -product org.eclipse.epp.package.cpp.product
Command-line arguments:  -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.cpp.product

This is a continuation of log file D:\Profiles\ems019\workspace_v5_1\.metadata\.bak_0.log
Created Time: 2011-10-28 15:41:14.345

 

java.lang.NullPointerException
    at org.eclipse.jface.dialogs.DialogPage.getShell(DialogPage.java:295)
    at org.eclipse.cdt.ui.newui.AbstractPage.handleResize(AbstractPage.java:830)
    at org.eclipse.cdt.ui.newui.AbstractPage.dispose(AbstractPage.java:985)
    at com.ti.common.project.ui.properties.ConfigurationPropertiesPage.dispose(ConfigurationPropertiesPage.java:94)
    at org.eclipse.jface.preference.PreferenceNode.disposeResources(PreferenceNode.java:173)
    at org.eclipse.jface.preference.PreferenceDialog$2.run(PreferenceDialog.java:301)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
    at org.eclipse.jface.preference.PreferenceDialog.close(PreferenceDialog.java:315)
    at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.close(FilteredPreferenceDialog.java:697)
    at org.eclipse.jface.preference.PreferenceDialog$13.run(PreferenceDialog.java:986)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
    at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49)
    at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
    at org.eclipse.jface.preference.PreferenceDialog.okPressed(PreferenceDialog.java:944)
    at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.okPressed(FilteredPreferenceDialog.java:447)
    at org.eclipse.jface.preference.PreferenceDialog.buttonPressed(PreferenceDialog.java:233)
    at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
    at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:240)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
    at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4165)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3754)
    at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
    at org.eclipse.jface.window.Window.open(Window.java:801)
    at org.eclipse.ui.dialogs.PropertyDialogAction.run(PropertyDialogAction.java:158)
    at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
    at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
    at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
    at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
    at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4165)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3754)
    at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696)
    at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660)
    at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494)
    at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674)
    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
    at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667)
    at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
    at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123)
    at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1410)

 

 

  • 0
    TI__Guru*** 130875 points

    Hi Matt,

    we are going to try and investigate this for/with you.   Would you be able to zip and send any .dmp files and error logs generated?  Please keep us informed whether a new workspace/project also starts showing this behaviour.   I am going to attempt to reproduce the problem myself.  

    What version of the C6000 compiler are you using?  Did you end up independently installing Code Generation Tools for it?  Approximately how many include paths are you managing?  Do you have a sense of whether this occurs after a certain volume of paths added?

    Best Regards,
    Lisa

  • 0 in reply to Lisa TI
    Intellectual 530 points

    Hi Lisa,

    Thanks for your assistance.  I did not install the CGtools separately.  Currently it seems to be using 7.3.0.

    I've had some minor progress with the issue.   I've found that when I start up eclipse from the beginning, I have one error-free opportunity to access the project properties.   I can add edit whatever I want.   After that, the eclipse errors shown above happen with each one.

    The number of include paths, in the end will probably be around 9 or 10 paths.   Enclosed is the zip file.

    Again, thanks for your help,

     

    Br,
    Matt

     

     

    bak_0.zip
  • 0 in reply to mes
    TI__Guru*** 130875 points

    Hi Matt,

    I did a bit of digging here in our team and determined that this seems to be a bug that was discovered and fixed.

    Actually if you upgrade to RC1 (which is why I could not reproduce the issue), you should find that the problem is fixed without even having to recreate your projects.

    Would you be able to give this a try and confirm?

    Best Regards,
    Lisa

  • 0 in reply to Lisa TI
    Intellectual 530 points

    Hi Lisa,

    That's great news - So when I originally installed 5.1, I went to the help menu and clicked check for updates and installed what it found.   I just did this again and it says 'no new updates'

    I get now that this isn't hooked up to the CCS portion of the tool (holdover from 3.3).   It's downloading now from the wiki site. I'll let you know as soon as it is finished.

    Br,
    Matt

  • 0 in reply to mes
    Intellectual 530 points

    Lisa,

    It looks fixed.  For the post mortem, I think I didn't know that the help->check for updates didn't cover the actual CCS plug in.   Will it in the future?  No matter, I will just check the wiki periodically. 

    Thanks again for your help,

    Br,

    Matt

  • 0 in reply to mes
    TI__Guru*** 130875 points

    Hi Matt,

    I am glad to hear that things seem to be working better for you in the latest release.

    Do keep an eye on the wiki posts.  They will being updated as v5 becomes the production version and a full release.  I suspect that might also explain the update situation, but one main difference with v5 is that we use stock eclipse now.

    All the best with development.

    Best Regards,
    Lisa