OMSimulator crashes when FMU sends a log message without a category

[rruusu]

Description

The FMI standard allows an FMU to call the logging function with a null pointer for the category, if it doesn't defined any categories.

When this happens, OMSimulator crashes, as it does not check for a null value in the category argument in its logging function.

When executed using the command line omsimulator executable, the crash is silent and produces no related console prints.

Steps to reproduce

1. Simulate an SSP containing FMUs producing messages with category NULL.
2. OMSimulator crashes silently, retuning a seemingly random exit status

Example:

C:\...>omsimulator Demo_ss3.ssp --logLevel=1 || echo Error: %errorlevel%
...
Error: -1073741819

Version and OS

• Version: OMSimulator v2.1.2-mingw-notlm-debug
• OS: Windows 11, 64-bit

[rruusu]

The culprit is function void oms::fmi2logger(fmi2ComponentEnvironment env, fmi2String instanceName, fmi2Status status, fmi2String category, fmi2String message, ...) in Component.cpp.

[arun3688]

@rruusu It would be good if you can attach your ssp or Fmu's which can reproduce the issue, if you cannot share your model or ssp make a small fmu which can reproduce the issue