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.

Launching Debug Server (DSS) fails from latest Matlab (R2011b)

Other Parts Discussed in Thread: CCSTUDIO

Launching Debug Server via the java interface from Matlab versions R2010a and R2011a both work fine, but from R2011b, it now has an error:

java.lang.SecurityException: class "org.mozilla.interfaces.dsIDebugger"'s signer information does not match signer information of other classes in the same package  (0x80004005)

I guess Matlab 2011b has somehow increased security or checking on running JAR files...not really sure.  Does anyone know what to do here?  Searching on the web, suggestions for this java error seem to be either to re-arrange the order of jar files loaded in the classpath, or by somehow re-signing or removing the manifest of the java packages.  I don't know how to proceed...

Thanks,

ML

  • Michael,

    I don't believe that is one of our packages as the class name starts with org.mozilla.  The class for the TI debug server would start with something like com.ti.  Probably best to follow up with the Mathworks.

    John

  • well, here's a listing of the JAR files in the TI DSS installation, note the last file MozillaInterfaces.jar:

    C:\Program Files\Texas Instruments\ccsv4\DebugServer\packages\ti\dss\java

    com.ti.ccstudio.scripting.environment_3.1.0.jar
    com.ti.ccstudio.scripting.rtdx_1.0.0.jar
    com.ti.debug.engine.linux.kernel_1.0.0.jar
    com.ti.debug.engine_1.0.0.jar
    dss.jar
    js.jar
    MozillaInterfaces.jar

    I think this all simply has to do with creating a proper Java XPCOM interface -- to correct the error, I would think the JAR files need to be re-built with a properly signed manifest.

    I will  also submit the error to Mathworks, but I'm sure if you can contact whoever builds your Java XPCOM inteface, they would sure recognize this kind of error message.

    Thanks, Mike


     

     

  • Mike I will check with our debugger guys.

  • Mike

    The guy here provided a good explanation of what causes this exception.

    Note (1): TI does not compile MozillaInterfaces.jar - we just copy it around. Note (2): the MozillaInterfaces.jar in the CCS folder isn't signed.

    So, it seems invoking the latest version of Matlab causes a Mozilla jar to be loaded that has a different signature than the a Mozilla jar CCS uses. If this is correct, it is going to cause problems on multiple levels - not just the signing issue. CCS uses XPCOM underneath. Everyone in the same process space must use the same version of XPCOM loaded from the same location or things are not going to work correctly.  On Linux, the embedded browser in Eclipse also uses XPCOM, so even with CCS not in the picture there would be a potentail conflict. 

    I'm trying to find a contact at Matlab that could help understand what is loading the other Molliza content (if this is indeed what is happening), and if there is anything that could be done to prevent it.

  • Thanks, this helps to start narrowing down the error.  Note that one of the lines in my Matlab script is trying to set the XPCOM path:

    System.setProperty('XPCOM.RUNTIME', 'C:\Program Files\Texas Instruments\ccsv4\DebugServer\win32' )

    For now, I'll see if I can get more information on the possible conflict.

    Thanks,

    ML

  • Thanks,

    I "fixed" the issue by commenting out two of the lines in "C:\Program Files\MATLAB\R2011b\toolbox\local\classpath.txt":

    $matlabroot/java/jarext/jxbrowser/MozillaGlue.jar
    $matlabroot/java/jarext/jxbrowser/MozillaInterfaces.jar

    In going to R2011b, Matlab added the above references which had not previously existed.  This indeed causes the conflict with the TI DSS java objects.

    Thanks,
    ML