If a non-existent INI file was passed to bare_etiss_processor, ETISS just print Initializer::loadIni(): Failed to load Ini: ... and ignores that error. Depending on the relevance of the INI file this will lead to a crash when starting the simulation (i.e. unset arch.cpu) or just lead to infinite errors (i.e. missing/wrong memsegs).
https://github.com/tum-ei-eda/etiss/blob/master/src/ETISS.cpp#L375-L377
Shouldn't we make this an "fatal error" and call abort() is this happens?
@JoGei @jokap11
If a non-existent INI file was passed to
bare_etiss_processor, ETISS just printInitializer::loadIni(): Failed to load Ini: ...and ignores that error. Depending on the relevance of the INI file this will lead to a crash when starting the simulation (i.e. unsetarch.cpu) or just lead to infinite errors (i.e. missing/wrong memsegs).https://github.com/tum-ei-eda/etiss/blob/master/src/ETISS.cpp#L375-L377
Shouldn't we make this an "fatal error" and call
abort()is this happens?@JoGei @jokap11