Hi, correction: While the problem described below exists, the current crashes are not random but related to the use of messages in "Chart" stateflow blocks in Simulink.
The whole thing seems like a bug, I just cannot say if it is Matlab or Etherlab. The problem didn't exist a week or two ago, now a Chart containing a message crashes Matlab when compiling with the etherlab target. As I didn't change my Matlab installation, but pulled an update for my system some time ago, I guess the problem is caused by some change in the etherlab toolchain. If you are interested, you will find two minimum examples attached, one that crashes and one that doesn't crash. Note that once Matlab crashed, it will crash every time until all compile files are deleted (folders slprj and <model>_etl_hrt). I am using openSUSE 15.2 with Linux 5.3.18-lp152.3.14-rt, the current etherlab environment from the openSUSE repository and Matlab R2020a. All the best, Amos -- Amos Merkel, M.Sc. Gruppenleiter Digitalisierung ifas - Institut für fluidtechnische Antriebe und Systeme RWTH Aachen University Campus-Boulevard 30 52074 Aachen Tel: +49 241 80-47737 Fax: +49 241 80-647712 www.ifas.rwth-aachen.de<http://www.ifas.rwth-aachen.de/> | Twitter<https://twitter.com/IFAS_RWTH> | Facebook<https://www.facebook.com/IFAS-Institut-f%C3%BCr-fluidtechnische-Antriebe-und-Steuerungen-260714043957873/> | YouTube<https://www.youtube.com/channel/UC0vIq8jtra8E_--Sx8DALkQ> | LinkedIn<http://www.linkedin.com/company/ifas-rwth/> Von: Etherlab-users <etherlab-users-boun...@etherlab.org> Im Auftrag von Merkel, Amos Gesendet: Dienstag, 30. August 2022 13:41 An: etherlab-users@etherlab.org Betreff: [Etherlab-users] Random Matlab crashes with Stateflow Hi everyone, I am using the Etherlab environment together with the etherlab Simulink library. For the actual program procedure, I rely mostly on the Stateflow blocks in Simulink. Usually this works quite well, but I have encountered random crashes while compiling several times now. Typically it is an working Simulink file, you do a small change and encounter the crashes. Reverting the change does not solve the issue, however deleting the stateflow block does. Copy & pasting the stateflow block to another model crashes that one as well, reprogramming the stateflow block exactly the same, but from scratch without copy+pasting anything works without problem. Does anybody now this effect, or a better solution than programming everything anew? All the best, Amos -- Amos Merkel, M.Sc. Group leader Digitalization ifas - Institute for Fluid Power Drives and Systems RWTH Aachen University Campus-Boulevard 30 52074 Aachen Tel: +49 241 80-47737 Fax: +49 241 80-647712 www.ifas.rwth-aachen.de<http://www.ifas.rwth-aachen.de/> | Twitter<https://twitter.com/IFAS_RWTH> | Facebook<https://www.facebook.com/IFAS-Institut-f%C3%BCr-fluidtechnische-Antriebe-und-Steuerungen-260714043957873/> | YouTube<https://www.youtube.com/channel/UC0vIq8jtra8E_--Sx8DALkQ> | LinkedIn<https://www.linkedin.com/company/ifas-rwth/> -- Amos Merkel, M.Sc. Gruppenleiter Digitalisierung ifas - Institut für fluidtechnische Antriebe und Systeme RWTH Aachen University Campus-Boulevard 30 52074 Aachen Tel: +49 241 80-47737 Fax: +49 241 80-647712 www.ifas.rwth-aachen.de<http://www.ifas.rwth-aachen.de/> | Twitter<https://twitter.com/IFAS_RWTH> | Facebook<https://www.facebook.com/IFAS-Institut-f%C3%BCr-fluidtechnische-Antriebe-und-Steuerungen-260714043957873/> | YouTube<https://www.youtube.com/channel/UC0vIq8jtra8E_--Sx8DALkQ> | LinkedIn<http://www.linkedin.com/company/ifas-rwth/>
matlab_crash_dump.23232-1
Description: matlab_crash_dump.23232-1
Minimum_Crash_R2013a.slx
Description: Minimum_Crash_R2013a.slx
Minimum_NoCrash_R2013a.slx
Description: Minimum_NoCrash_R2013a.slx
-- Etherlab-users mailing list Etherlab-users@etherlab.org https://lists.etherlab.org/mailman/listinfo/etherlab-users
