OMEdit crashes when editing OMSimulator model

[Andreas Heuermann]

I'm trying to add a connector between testInput.integertable1.y and simpleTest.u where testInput is a submodule of CSV file (simulated testInput.mo) and simpleTest is a submodule of an ME 2.0 FMU (generated from simpleTest.mo).

After I get a scripting error

[addConnection] Type mismatch in connection: testInput.integertable1.y .> simpleTest.u

OMEdit will crash. Please see attached screenshot.

SimpleTest.mo

model SimpleTest "just a simple model - Compilation etc."
  Modelica.Blocks.Interfaces.IntegerInput u;
  Modelica.Blocks.Interfaces.IntegerOutput y;
algorithm
  when u > pre(u) then
    y := y + 2;
  end when;
end SimpleTest;

testInput.mo

model testInput
  Modelica.Blocks.Sources.IntegerTable integertable1(table=[0, 1; 0.2, 2; 0.4, 3; 0.6, 4; 0.8, 5; 1, 6]);
end testInput;

I'm running OpenModelica v1.16.0-dev-106-gf60ffbd0a (64-bit)
Connected to OMSimulator v2.1.0-dev-147-g36ec2c7-mingw on Windows 10

[Andreas Heuermann]

Crash of OMEdit after error cathed by OMSimulator

[Andreas Heuermann]

While trying to safe the spp file to add as example OMEdit crashes also. See the next screenshot.

[Andreas Heuermann]

OMEdit crashes wile savig spp file

[Francesco Casella]

It could be interesting to see the stacktrace. Tools | Open Working Directory, then attach omedit*.log and omedit*.txt files to this ticket.

[Andreas Heuermann]

Logs from OMEdit working directory

[Andreas Heuermann]

The central error is presumably

terminate called after throwing an instance of 'std::runtime_error'
  what():  Failed to copy file: C:/Users\USERNAME\AppData\Local\Temp\OpenModelica\OMEdit\simulateWithOMSimulator-4scj5a1n\temp/model.ssp  to: D:/workspace/Testitesttest/ticket5785/simulateWithOMSimulator.ssp

from omediterror.txt.

[Andreas Heuermann]

My generated test FMU

[Adeel Asghar]

This is not an issue of OMEdit. I traced it back to OMSimulator core and created an issue on OMSimulator github ​https://github.com/OpenModelica/OMSimulator/issues/715.

[Andreas Heuermann]

But I still would prefer whenever OMSimulator throws std::runtime_error to catch the error and at least give some more output on what happend.

Is this possible?