setDebugLogging on 2.5 RC2 induces JRE fatal error

[Former user]

When use setDebugLogging with a categorie name induces JRE fatal error (EXCEPTION_ACCESS_VIOLATION)

Here is my code:

Simulation emtp = new Simulation("fmu/testCase1.fmu");

    Access access = new Access(emtp);

    String[] logCat = new String[1];
    logCat[0] = "logAll";
    access.setDebugLogging(true, logCat.length, logCat);

[Johan Cortés]

We have done this test with our FMUs and it works, so with only this information it is not possible to reproduce the issue. Please provide us more details about:

System architecture JavaFMI version Java Runtime Environment and it is very important for us the FMU to test.

We will understand if you are not able to distribute the FMU but without it is not possible to reproduce the test.

Thank you very much

[Jose Evora]

We don't have enough information