@KICAD_user can you upload a project which shows this? I tried "Sallen_Key" and "QEI", but they both worked fine (and most of my other simulation tests don't include workbooks).
Oh wait, you're not even getting to the Open File dialog? That sounds more like a menu issue. Can you get a stack-trace?
Even without being able to reproduce it, this code is fishy, we are indexing into C-style arrays unchecked in SIM_PLOT_PANEL::addTrace which is not great, so at minimum any caller of addTrace needs to bounds-check the aX and aY arrays.
Even fixing the file path issue, I still don't get a crash on Linux. The path separator is another bug. Is this possibly yet another Windows built with MSVC only bug? @charrasjp are you seeing this on your msys2 builds?
I agree that would should not blindly be attempting to access an array without bound checking just like we shouldn't blindly assume that pointers are valid.
I'm getting a simulation failure so I'm guessing there are no trace points. The question then would be why is this code being called when the simulation fails?
It seems to me that the wxASSERT_MSG( false, wxT( "Plot type missing AC_PHASE or AC_MAG bit" ) ); in SIM_PLOT_FRAME::updatePlot() needs to return, not break. Otherwise we get to addPlot with an empty data_y.
Is this assert firing for those who see it crashing?