• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 52 subscribers
  • Views 1465 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

IllegalArgumentException when using DSS (with CCS monitor) over JVM from C++ DLL

Björn Ahrends
Prodigy 160 points
Other Parts Discussed in Thread: CCSTUDIO

Hi everybody,

I'm working on an automated test environment using CCS4. In this environment a C++ DLL starts a JVM (including a classpath containing a self written java class, which simply wraps all needed debuging functionality from the CCS4 classes into a single class) and within this Virtual Machine the DSS takes place. Furthermore CCS4 is started (by including CCS's startup.jar) in order to actually see the debug activity.

Everything works fine except following error message when CCS4 starts:

java.lang.IllegalArgumentException: Path not found.
    at com.ti.debug.engine.xpcom.Runtime.startBare(Runtime.java:102)
    at com.ti.debug.engine.xpcom.Runtime.startBare(Runtime.java:77)
    at com.ti.debug.engine.xpcom.Runtime.createComponent(Runtime.java:160)
    at com.ti.license.impl.LicenseManager.<init>(LicenseManager.java:111)
    at com.ti.debug.engine.cce.LicenseEngine.<init>(LicenseEngine.java:20)
    at com.ti.debug.engine.cce.LicenseEngine.createInstance(LicenseEngine.java:28)
    at com.ti.ccstudio.debug.server.extensions.ExtLicenseManager.createInstance(ExtLicenseManager.java:24)
    at com.ti.ccstudio.debug.server.factory.LicenseEngineFactory.createInstance(LicenseEngineFactory.java:14)
    at com.ti.ccstudio.update.CCEUpdateStartup.heartbeat(CCEUpdateStartup.java:34)
    at com.ti.ccstudio.update.CCEUpdateStartup.earlyStartup(CCEUpdateStartup.java:13)
    at org.eclipse.ui.internal.EarlyStartupRunnable.runEarlyStartup(EarlyStartupRunnable.java:87)
    at org.eclipse.ui.internal.EarlyStartupRunnable.run(EarlyStartupRunnable.java:66)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
    at org.eclipse.ui.internal.Workbench$20.run(Workbench.java:1759)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)

Following parameters are handed over to JVM:

-DXPCOM.RUNTIME="C:\Program Files\Texas Instruments\ccsv4\DebugServer\win32"

-Djava.class.path=
%%%my_class%%%;
C:\Program Files\Texas Instruments\ccsv4\DebugServer\packages\ti\dss\java\com.ti.ccstudio.scripting.environment_3.1.0.jar;
C:\Program Files\Texas Instruments\ccsv4\DebugServer\packages\ti\dss\java\com.ti.debug.engine_1.0.0.jar;
C:\Program Files\Texas Instruments\ccsv4\DebugServer\packages\ti\dss\java\dss.jar;
C:\Program Files\Texas Instruments\ccsv4\eclipse\startup.jar

-Dcom.sun.management.jmxremote

(JMXRemote is handed over in order to connect to the JVM via JConsole) The path to XPCom runtime is correct... The same path is used for testing the simple wrapping class (mentioned above) within Eclipse IDE without any errors.

Due to the error it is not possible to connect to the attached debugger because it's not shown in the list of available debuggers.

So my question is, if I have to append additional paths to the class path parameter? Or which path is missing?

 

Thanks,

Bjoern

  • 0
    Prodigy 160 points

    Appending followings JARs to the classpath didn't work either:

    C:\Program Files\Texas Instruments\ccsv4\DebugServer\packages\ti\dss\java\MozillaInterfaces.jar
    C:\Program Files\Texas Instruments\ccsv4\DebugServer\packages\ti\dss\java\com.ti.ccstudio.scripting.rtdx_1.0.0.jar
    C:\Program Files\Texas Instruments\ccsv4\DebugServer\packages\ti\dss\java\com.ti.debug.engine.linux.kernel_1.0.0.jar
    C:\Program Files\Texas Instruments\ccsv4\DebugServer\packages\ti\dss\java\js.jar

  • 0
    Prodigy 160 points

    Problem solved:

    While eg. class paths for the JVM can be set using double backslashes like follows:

    "\\DebugServer\\packages\\ti\\dss\\java\\com.ti.debug.engine_1.0.0.jar"

    CCS accepts for its XPCOM Path only slahes:

    "-DXPCOM.RUNTIME=C:/Program Files/Texas Instruments/ccsv4/DebugServer/win32/"