• Locked Locked
  • Replies 8 replies
  • Subscribers 53 subscribers
  • Views 1612 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.

Cannot launch debugger in CCSv5.1.1 - Error within Debug UI

Stephen Wells
Prodigy 220 points

Does anyone know what causes this Exception when launching a debug session:

Exception occurred during launch

Reason:

Error within Debug UI

Details state: java.lang.reflect.InvocationTargetException and I have no way of looking at the java stack trace or getting to the cause.

Once this failure appears, I have not found a way out except going back to an earlier Linux VM where it worked.

Is this an Eclipse issue?

Testing the connection from the Target Configuration '.ccxml' file always works fine.

OS: Ubuntu 10.04 LTS

CCS v5.1.1.00033

Java:

java -version
java version "1.6.0_20"
OpenJDK Runtime Environment (IcedTea6 1.9.13) (6b20-1.9.13-0ubuntu1~10.04.1)
OpenJDK Client VM (build 19.0-b09, mixed mode, sharing)


  • TI__Guru*** 130875 points

    Hi Stephen,

    Have you tried updating your JRE?  Have you tried a reinstallation?  Are you using 64 bit or 32 bit Ubuntu?  (If 64 bit you will need the 32 bit support package as described in this topic)

    http://processors.wiki.ti.com/index.php/Linux_Host_Support#Installation_Instructions

    Did you ensure all required dependencies are installed?  Can you send us any error logs or dump files generated?

    Can you run debug server script examples independant of CCS?

    Best Regards,
    LIsa

  • in reply to Lisa TI
    Prodigy 220 points

    Hi Lisa,

    Ubuntu v10.04 LTS 32bit

    So far:

    Re-installed CCS, deleted metadata from workspace. (Have not tried a new workspace yet)

    Using Synaptic Package Manager, removed Openjdk-6-jdk (and all the jre) and re-installed.

    No change

    I created a new HelloWorld CCS native project to run on my hardware and it appears to work.

    My test project still fails, they use the same target configuration file but obviously different debug configs.

    HelloWorld uses the TI toolchain

    My test project uses the arm-eabi toolchain

    This logfile (attached) was active whilst building and debug Hello World, then my boot loader test program.

    Fullscreen 1385.log.txt Download 
    !SESSION 2012-03-21 13:06:02.631 -----------------------------------------------
eclipse.buildId=M20110909-1335
java.version=1.6.0_13
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
Framework arguments:  -product com.ti.ccstudio.branding.product
Command-line arguments:  -os linux -ws gtk -arch x86 -product com.ti.ccstudio.branding.product

!ENTRY com.ti.ccstudio.scripting.console 2 0 2012-03-21 13:06:11.105
!MESSAGE Failed to setActiveScriptContext for class org.eclipse.rtsc.xdctools.model.ui.scripting.XGCONFScriptingService
!STACK 0
java.lang.AbstractMethodError
	at com.ti.ccstudio.scripting.console.internal.Activator.setActiveScriptContext(Activator.java:94)
	at com.ti.ccstudio.scripting.console.internal.Startup$1.safeRun(Startup.java:53)
	at com.ti.ccstudio.rhino.SafeRunnable.run(SafeRunnable.java:27)
	at com.ti.ccstudio.rhino.internal.RhinoThreadExecutor$1.run(RhinoThreadExecutor.java:67)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)
	at com.ti.ccstudio.rhino.internal.RhinoThreadExecutor$RhinoThread.run(RhinoThreadExecutor.java:88)

!ENTRY com.ti.ccstudio.scripting.console 2 0 2012-03-21 13:06:14.610
!MESSAGE Failed to setActiveScriptContext for class org.eclipse.rtsc.xdctools.model.ui.scripting.XGCONFScriptingService
!STACK 0
java.lang.AbstractMethodError
	at com.ti.ccstudio.scripting.console.internal.Activator.setActiveScriptContext(Activator.java:94)
	at com.ti.ccstudio.scripting.console.internal.Startup$2$1.safeRun(Startup.java:100)
	at com.ti.ccstudio.rhino.SafeRunnable.run(SafeRunnable.java:27)
	at com.ti.ccstudio.rhino.internal.RhinoThreadExecutor$1.run(RhinoThreadExecutor.java:67)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)
	at com.ti.ccstudio.rhino.internal.RhinoThreadExecutor$RhinoThread.run(RhinoThreadExecutor.java:88)

!ENTRY org.eclipse.update.core 4 0 2012-03-21 13:06:17.578
!MESSAGE Site already exists.

!ENTRY org.eclipse.update.core 4 0 2012-03-21 13:06:17.578
!MESSAGE Site already exists.

!ENTRY org.eclipse.update.core 4 0 2012-03-21 13:06:17.578
!MESSAGE Site already exists.

!ENTRY org.eclipse.update.core 4 0 2012-03-21 13:06:17.579
!MESSAGE Site already exists.

!ENTRY org.eclipse.update.core 4 0 2012-03-21 13:06:17.579
!MESSAGE Site already exists.

!ENTRY org.eclipse.osgi 2 0 2012-03-21 13:06:20.071
!MESSAGE While loading class "com.ti.dvt.rovsupport.ROVPlugin$2", thread "Thread[main,6,main]" timed out waiting (5068ms) for thread "Thread[Worker-9,5,main]" to finish starting bundle "com.ti.dvt.rovsupport_3.1.0.201201192237 [409]". To avoid deadlock, thread "Thread[main,6,main]" is proceeding but "com.ti.dvt.rovsupport.ROVPlugin$2" may not be fully initialized.
!STACK 0
org.osgi.framework.BundleException: State change in progress for bundle "reference:file:plugins/com.ti.dvt.rovsupport_3.1.0.201201192237.jar" by thread "Worker-9".
	at org.eclipse.osgi.framework.internal.core.AbstractBundle.beginStateChange(AbstractBundle.java:1087)
	at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:297)
	at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:440)
	at org.eclipse.osgi.internal.loader.BundleLoader.setLazyTrigger(BundleLoader.java:268)
	at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107)
	at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:462)
	at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:216)
	at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:400)
	at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:476)
	at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:429)
	at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417)
	at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
	at java.lang.ClassLoader.loadClass(Unknown Source)
	at java.lang.ClassLoader.loadClassInternal(Unknown Source)
	at com.ti.dvt.rovsupport.ROVPlugin.getPartListener(ROVPlugin.java:739)
	at com.ti.dvt.rovsupport.ROVPlugin$4.run(ROVPlugin.java:946)
	at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
	at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3563)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3212)
	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)
Caused by: org.eclipse.osgi.framework.internal.core.AbstractBundle$BundleStatusException
	... 40 more
Root exception:
org.eclipse.osgi.framework.internal.core.AbstractBundle$BundleStatusException
	at org.eclipse.osgi.framework.internal.core.AbstractBundle.beginStateChange(AbstractBundle.java:1087)
	at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:297)
	at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:440)
	at org.eclipse.osgi.internal.loader.BundleLoader.setLazyTrigger(BundleLoader.java:268)
	at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107)
	at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:462)
	at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:216)
	at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:400)
	at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:476)
	at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:429)
	at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417)
	at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
	at java.lang.ClassLoader.loadClass(Unknown Source)
	at java.lang.ClassLoader.loadClassInternal(Unknown Source)
	at com.ti.dvt.rovsupport.ROVPlugin.getPartListener(ROVPlugin.java:739)
	at com.ti.dvt.rovsupport.ROVPlugin$4.run(ROVPlugin.java:946)
	at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
	at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3563)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3212)
	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)

!ENTRY com.ti.gde.adapter.c6flo 1 0 2012-03-21 13:06:20.618
!MESSAGE install directory: /opt/ti/ccsv5/eclipse

!ENTRY com.ti.gde.adapter.c6flo 1 0 2012-03-21 13:06:20.618
!MESSAGE blocksDirectory directory: /opt/ti/ccsv5/ccs_base/c6flo_1.0.0.201201192237/Blocks

!ENTRY com.ti.gde.adapter.c6flo 1 0 2012-03-21 13:06:20.646
!MESSAGE xdcToolLocation directory: NULL

!ENTRY com.ti.gde.diagram 1 0 2012-03-21 13:06:20.646
!MESSAGE GDE adapter found: com.ti.gde.adapter.c6flo.C6floAdapter   Supporting extensions: [c6flo] PluginID=com.ti.gde.adapter.c6flo

!ENTRY com.ti.gde.adapter.c6flo 4 0 2012-03-21 13:06:20.707
!MESSAGE Problem Reading component Definitions
!STACK 0
java.lang.NullPointerException
	at java.util.Hashtable.put(Unknown Source)
	at java.util.Properties.setProperty(Unknown Source)
	at org.eclipse.rtsc.xdctools.model.db.ModelDB.getEnv(ModelDB.java:128)
	at org.eclipse.rtsc.xdctools.model.db.ModelDB.getProperties(ModelDB.java:118)
	at com.ti.gde.adapter.c6flo.C6FloPackagesReader.readPackages(C6FloPackagesReader.java:50)
	at com.ti.gde.adapter.c6flo.C6floAdapter.doInit(C6floAdapter.java:216)
	at com.ti.gde.adapter.interfaces.GdeAdapter.init(GdeAdapter.java:49)
	at com.ti.gde.diagram.plugin.GdeDiagramEditorPlugin$1.run(GdeDiagramEditorPlugin.java:467)

!ENTRY org.eclipse.core.jobs 4 2 2012-03-21 13:07:19.949
!MESSAGE An internal error occurred during: "Launching debug-boot-loader".
!STACK 0
java.lang.NullPointerException
	at com.ti.common.project.core.internal.CommonProjectCorePlugin.getDelegateFactory(CommonProjectCorePlugin.java:491)
	at com.ti.common.project.core.internal.CommonProjectCorePlugin.getToolChainPropertyProvider(CommonProjectCorePlugin.java:478)
	at com.ti.common.project.core.util.CTIProjectCoreUtils.getToolChainPropertyProvider(CTIProjectCoreUtils.java:415)
	at com.ti.common.project.core.util.CTIProjectCoreUtils.getConfigurationSettings(CTIProjectCoreUtils.java:975)
	at com.ti.common.project.core.util.CTIProjectCoreUtils.getDependencies(CTIProjectCoreUtils.java:1070)
	at com.ti.common.project.core.util.CTIProjectCoreUtils.getDependencies(CTIProjectCoreUtils.java:1085)
	at com.ti.ccstudio.debug.launch.CCSLaunchDelegate.addReferencedProjects(CCSLaunchDelegate.java:497)
	at com.ti.ccstudio.debug.launch.CCSLaunchDelegate.getAllProjects(CCSLaunchDelegate.java:290)
	at com.ti.ccstudio.debug.launch.CCSLaunchDelegate.getProjectsForProblemSearch(CCSLaunchDelegate.java:281)
	at com.ti.ccstudio.debug.launch.CCSLaunchDelegate.getBuildOrder(CCSLaunchDelegate.java:439)
	at org.eclipse.debug.core.model.LaunchConfigurationDelegate.saveBeforeLaunch(LaunchConfigurationDelegate.java:255)
	at com.ti.ccstudio.debug.launch.CCSLaunchDelegate.preLaunchCheck(CCSLaunchDelegate.java:213)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:809)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703)
	at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:928)
	at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1132)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
     

    The debug session launch fails - see last exception.

    Any ideas?

    Thanks

    Steve

  • in reply to Stephen Wells
    TI__Guru*** 130875 points

    Hi Stephen,

    what target are you working with?   So do I understand correctly that the built in example does not show this behaviour?  What do you mean by the difference in the two "toolchains". Can you be more specific?

    Best Regards,
    Lisa

  • in reply to Lisa TI
    Prodigy 220 points

    My target board has some similarities to the Beagleboard-XM so it's convenient to base a boot loader on the x-loader Linux project, the GNU (GCC) tool chain for this come from the TI devkit (arm-eabi-4.4.3) :).

    The project can be built on the command line and via Eclipse CDT or CCS - imported as 'makefile project with source' essentially using Eclipse as an editor and CCS for XDS560v2 STM ICE & debugger interface.

    The CCS debugger has been largely successful (just some GEL files porting to match my hardware) and very helpful over the last few months, but this issue keeps coming up, this time I'm forced to try and fix it . . . all I know is as soon as I attempt to launch the debug session is fails - almost instantly, as if some xml config is invalid or NULL or pointing to NULL - anyway, I checked the log file and the exception is visible - but I need developer help to determine it's source.

    Makes me wonder how, by chance it worked in the past!

    Regards

    Steve

    P.S I could set up a Cisco WebEx session?



  • in reply to Stephen Wells
    TI__Guru*** 130875 points

    Hi Steve,

    sorry for the delay in response.  What I find odd is that you have a VM image where this works, is that correct?  So what is the difference between that and the non working image?  Could something have been corrupted? 

    Let me check with a few colleagues here to see what other thoughts we might have.

    Best Regards,

    Lisa

  • in reply to Stephen Wells
    TI__Guru**** 463981 points

    Hi Steve,

    If I am getting all this correctly, you run into issues only when trying to start a project debug session for your project that uses a different tool-chain. When you start a project-less debug session using the same target configuration or a project debug session with a different project, the debugger starts fine. I would guess that this a potential corruption of your project launch configuration. However those are stored in your workspace and you have mentioned you tried cleaning out your workspace with no success. One other thing to try is if you can start a project-less debug session and then manually load the executable and see if that will load correctly. If so, then the generated executable is not causing the crash and it is something specific to the debugger launch. Also, please provide a crash dump file and generate a debug server log (you need to explicitly enable this and reproduce the issue). These two files are very useful in trying to get more details as to the cause of the crash.

    http://processors.wiki.ti.com/index.php/Troubleshooting_CCSv5#CCS_Diagnostic_Logs

    Thanks

    ki

  • in reply to Ki
    Prodigy 220 points

    Hi ki,

    Issue has widened! Code download via XDS560v2 emulator fails . . .

    This is what I can get to work:

    • Out of the box hello world works well on my target, I used GEL files to start up the CPU clocks, pinmux, sdram etc.
    • Deleting the program entry from the debug configuration allows me to start a project less debug session ok (as you suggested - thanks!).
    • I have built (makefile) the linux x-loader project from the devkit and installed (as signed MLO) onto an SD card. It's modified to work on my target and flash an LED to say it's working ok.
    • Launching the debugger allows me to interact with a running x-loader booted via SDIO CARD (MLO file) and also Load dwarf symbols (yep LED still flashes).

    What I cannot get working (all built as instructed using arm-eabi-4.4.3 toolchain):

    • If I build the original (unmodified) x-loader with '-gstabs+' symbolic debug switch, then upon download via emulator (no execution), CCS (Windows or Linux platform) will just exit - gone! 
    • If I build the original (unmodified) x-loader with '-dwarf-2' symbolic debug switch, then upon download via emulator (no execution), CCS (Windows or Linux platform) - no crash but no actual code - just garbage where x-load.map says it should be. Symbols are ok.
    • If I build my modified x-loader with '-dwarf-2' symbolic debug switch (used for the SDCARD boot above), then upon download via emulator (no execution), CCS (Windows or Linux platform) still no actual code - just garbage where x-load.map says it should be. Symbols are again in the right places.
    • The original issue: If I create a debug configuration (clone of project less one) using x-loader elf output (so debugger downloads automatically on connect), it immediately fails with a 'java.lang.NullPointerException' exception as before.
    • Archiving log files generated: 
      An internal error occurred during: "Archiving Logs".
      java.lang.NullPointerException

    So from what I could find . . . 5270.Logs.zip

    The log files were recorded during: Original issue (debugger launch exception), loading x-loader (dwarf-2), then CCS exists with loading x-loader (gstabs+) .

    x-loader (unmodified) elf files used above:7318.x-load elf.zip

  • in reply to Stephen Wells
    Prodigy 220 points

    oh - one more log the eclipse .log