[Mission on Mars 2016 ] Simulink failed assertion after the first run

hi everybody. I have an issue about the simulation of the model. When I run thesimulation from first as matlab start there's no trouble. But after the end of the first simulation this followings errors appears and i have to restart matlab for start a new simulation wihtout trouble.

failed assertion in b:\matlab\src\eml\dom_eml\eml_path.cpp at line 1798:
  false
[  0] 0x00000000c261723d   C:\Program Files\MATLAB\R2015b\bin\win64\eml.dll+01798717 EML::NameCapture::updateMD5+00000621
[  1] 0x00000000f8f477bd C:\Program Files\MATLAB\R2015b\bin\win64\stateflow.dll+01144765 CGXE::JITMgr::JITMgr+00012781
[  2] 0x00000000f8f35fa2 C:\Program Files\MATLAB\R2015b\bin\win64\stateflow.dll+01073058 SF::StateflowTypeChecking::processFcn+00090418
[  3] 0x00000000f8f45f4a C:\Program Files\MATLAB\R2015b\bin\win64\stateflow.dll+01138506 CGXE::JITMgr::JITMgr+00006522
[  4] 0x00000000f936411e C:\Program Files\MATLAB\R2015b\bin\win64\stateflow.dll+05456158 SF::mx2str_write_str+00032974
[  5] 0x00000000f920f395 C:\Program Files\MATLAB\R2015b\bin\win64\stateflow.dll+04060053 SF::sf_mexFunction+00001301
[  6] 0x00000000f920ee92 C:\Program Files\MATLAB\R2015b\bin\win64\stateflow.dll+04058770 SF::sf_mexFunction+00000018
[  7] 0x00000000fc5f7551 C:\Program Files\MATLAB\R2015b\bin\win64\libmex.dll+00095569 mexRunMexFile+00000129
[  8] 0x00000000fc5f6872 C:\Program Files\MATLAB\R2015b\bin\win64\libmex.dll+00092274 inSwapMexfileReader+00000594
[  9] 0x00000000fc5f6426 C:\Program Files\MATLAB\R2015b\bin\win64\libmex.dll+00091174 mexUnlock+00004998
[ 10] 0x0000000014f34cc3 C:\Program Files\MATLAB\R2015b\bin\win64\m_dispatcher.dll+00019651 Mfh_file::dispatch_fh_impl+00000531
[ 11] 0x0000000014f3488e C:\Program Files\MATLAB\R2015b\bin\win64\m_dispatcher.dll+00018574 Mfh_file::dispatch_fh+00000062
[ 12] 0x0000000014f351e8 C:\Program Files\MATLAB\R2015b\bin\win64\m_dispatcher.dll+00020968 Mfunction_handle::dispatch+00000968
...
[122] 0x00000000fb5f84bb C:\Program Files\MATLAB\R2015b\bin\win64\libmwbridge.dll+00033979 ioReadLine+00000107
[123] 0x00000000fb603095 C:\Program Files\MATLAB\R2015b\bin\win64\libmwbridge.dll+00077973 mnDebugPrompt+00001509
[124] 0x00000000fb602bca C:\Program Files\MATLAB\R2015b\bin\win64\libmwbridge.dll+00076746 mnDebugPrompt+00000282
[125] 0x00000000fb6032eb C:\Program Files\MATLAB\R2015b\bin\win64\libmwbridge.dll+00078571 mnParser+00000395
[126] 0x0000000014e987a4   C:\Program Files\MATLAB\R2015b\bin\win64\mcr.dll+00362404 mcrInstance::mnParser_on_interpreter_thread+00000036
[127] 0x0000000014e6c477   C:\Program Files\MATLAB\R2015b\bin\win64\mcr.dll+00181367 mcr::runtime::setInterpreterThreadToCurrent+00019751
MATLAB stack trace:
> In verify_eml_resolved_functions (line 9)
  In get_autoinheritance_info>get_autoinheritance_info_possibly_invalid (line 52)
  In get_autoinheritance_info (line 5)
false
Component: Stateflow | Category: Assertion error
failed assertion in b:\matlab\src\eml\dom_eml\eml_path.cpp at line 1798:
  false
[  0] 0x00000000c261723d   C:\Program Files\MATLAB\R2015b\bin\win64\eml.dll+01798717 EML::NameCapture::updateMD5+00000621
[  1] 0x00000000f8f477bd C:\Program Files\MATLAB\R2015b\bin\win64\stateflow.dll+01144765 CGXE::JITMgr::JITMgr+00012781
[  2] 0x00000000f8f35fa2 C:\Program Files\MATLAB\R2015b\bin\win64\stateflow.dll+01073058 SF::StateflowTypeChecking::processFcn+00090418
[  3] 0x00000000f8f45f4a C:\Program Files\MATLAB\R2015b\bin\win64\stateflow.dll+01138506 CGXE::JITMgr::JITMgr+00006522
[  4] 0x00000000f936411e C:\Program Files\MATLAB\R2015b\bin\win64\stateflow.dll+05456158 SF::mx2str_write_str+00032974
[  5] 0x00000000f920f395 C:\Program Files\MATLAB\R2015b\bin\win64\stateflow.dll+04060053 SF::sf_mexFunction+00001301
[  6] 0x00000000f920ee92 C:\Program Files\MATLAB\R2015b\bin\win64\stateflow.dll+04058770 SF::sf_mexFunction+00000018
[  7] 0x00000000fc5f7551 C:\Program Files\MATLAB\R2015b\bin\win64\libmex.dll+00095569 mexRunMexFile+00000129
[  8] 0x00000000fc5f6872 C:\Program Files\MATLAB\R2015b\bin\win64\libmex.dll+00092274 inSwapMexfileReader+00000594
[  9] 0x00000000fc5f6426 C:\Program Files\MATLAB\R2015b\bin\win64\libmex.dll+00091174 mexUnlock+00004998
[ 10] 0x0000000014f34cc3 C:\Program Files\MATLAB\R2015b\bin\win64\m_dispatcher.dll+00019651 Mfh_file::dispatch_fh_impl+00000531
[ 11] 0x0000000014f3488e C:\Program Files\MATLAB\R2015b\bin\win64\m_dispatcher.dll+00018574 Mfh_file::dispatch_fh+00000062
[ 12] 0x0000000014f351e8 C:\Program Files\MATLAB\R2015b\bin\win64\m_dispatcher.dll+00020968 Mfunction_handle::dispatch+00000968
[ 13] 0x0000000015a37942 C:\Program Files\MATLAB\R2015b\bin\win64\m_lxe.dll+00162114
...
[124] 0x00000000fab0e5b8   C:\Program Files\MATLAB\R2015b\bin\win64\uiw.dll+00189880 UIW_ShowMenuItem+00006552
[125] 0x00000000fb5f94ac C:\Program Files\MATLAB\R2015b\bin\win64\libmwbridge.dll+00038060 ioReadLine+00004060
[126] 0x00000000fb5f86b4 C:\Program Files\MATLAB\R2015b\bin\win64\libmwbridge.dll+00034484 ioReadLine+00000484
[127] 0x00000000fb5f83f2 C:\Program Files\MATLAB\R2015b\bin\win64\libmwbridge.dll+00033778 ioCmdLineEditSave+00011986
MATLAB stack trace:
> In verify_eml_resolved_functions (line 9)
  In get_autoinheritance_info>get_autoinheritance_info_possibly_invalid (line 52)
  In get_autoinheritance_info (line 5)
false
Component: Stateflow | Category: Assertion error
failed assertion in b:\matlab\src\eml\dom_eml\eml_path.cpp at line 1798:
  false
[  0] 0x00000000c261723d   C:\Program Files\MATLAB\R2015b\bin\win64\eml.dll+01798717 EML::NameCapture::updateMD5+00000621
[  1] 0x00000000f8f477bd C:\Program Files\MATLAB\R2015b\bin\win64\stateflow.dll+01144765 CGXE::JITMgr::JITMgr+00012781
[  2] 0x00000000f8f35fa2 C:\Program Files\MATLAB\R2015b\bin\win64\stateflow.dll+01073058 SF::StateflowTypeChecking::processFcn+00090418
[  3] 0x00000000f8f45f4a C:\Program Files\MATLAB\R2015b\bin\win64\stateflow.dll+01138506 CGXE::JITMgr::JITMgr+00006522
[  4] 0x00000000f936411e C:\Program Files\MATLAB\R2015b\bin\win64\stateflow.dll+05456158 SF::mx2str_write_str+00032974
[  5] 0x00000000f920f395 C:\Program Files\MATLAB\R2015b\bin\win64\stateflow.dll+04060053 SF::sf_mexFunction+00001301
[  6] 0x00000000f920ee92 C:\Program Files\MATLAB\R2015b\bin\win64\stateflow.dll+04058770 SF::sf_mexFunction+00000018
[  7] 0x00000000fc5f7551 C:\Program Files\MATLAB\R2015b\bin\win64\libmex.dll+00095569 mexRunMexFile+00000129
[  8] 0x00000000fc5f6872 C:\Program Files\MATLAB\R2015b\bin\win64\libmex.dll+00092274 inSwapMexfileReader+00000594
[  9] 0x00000000fc5f6426 C:\Program Files\MATLAB\R2015b\bin\win64\libmex.dll+00091174 mexUnlock+00004998
[ 10] 0x0000000014f34cc3 C:\Program Files\MATLAB\R2015b\bin\win64\m_dispatcher.dll+00019651 Mfh_file::dispatch_fh_impl+00000531
[ 11] 0x0000000014f3488e C:\Program Files\MATLAB\R2015b\bin\win64\m_dispatcher.dll+00018574 Mfh_file::dispatch_fh+00000062
...
[127] 0x00000000fa9255b2   C:\Program Files\MATLAB\R2015b\bin\win64\mvm.dll+01004978 mvm::detail::SessionImpl::privateSession+00000962
MATLAB stack trace:
> In verify_eml_resolved_functions (line 9)
  In sync_eml_resolved_functions (line 78)
  In sync_target (line 115)
  In autobuild_kernel>compute_checksums (line 232)
  In autobuild_kernel>autobuild_local (line 152)
  In autobuild_kernel (line 57)
  In autobuild_driver (line 116)
  In slsf (line 116)
false
Component: Stateflow | Category: Assertion error
false
Component: Simulink | Category: Model error

I need help to fix it ! Thanks

[Clément Le Bihan]

Same Problem. Did you fix it ?

[Francisco Rodriguez]

Hi,

I've the same problem. Any idea to solve it?

Thanks.

[yunzhe su]

This is because you have used another user-defined function( notated function1) when you define user-defined function( notated function2).

solution:

step1: copy the code of function1 and paste after the code of function2

step2: restart your matlab（had better your computer）.

Answer 1

[Pavel Gureev]

I had exactly the same problem. Saying shortly, it occurs because of non-latin symbols in path. But things are not as simple as that. I've made some research to clarify the issue.

This error raises at the second and consequent launches of Simulink model, containing "MATLAB function block", that calls some user m-file function "bigFun.m" which in its turn calls another user m-file function "smallFun.m", one of which ("bigFun.m" or "smallFun.m") has non-latin symbols in path. Everything works fine, if inside "MATLAB function block" you call just "smallFun.m" that doesn't call other user functions, or if none of user function m-files, that is called from Simulink, contains non-latin symbols in path.

This is a very strange behaviour and I think it's a MATLAB-Simulink bug. I've tried at 2014, 2015 and 2016 versions, 32 and 64 bit.

As a temporary solution I can suggest two possible actions:

1. Move all m-file functions that are called from your Simulink model to a folder, which doesn't contain non-latin symbols in path

2. If you like your current project structure, don't want to move anything and you are used to launch your Simulink model from an init m-file, you can add a piece of code at the top of it:

projectName = 'latinProjectName';
mfPath = fileparts(mfilename('fullpath'));
myFunsPath = fullfile(mfPath, 'relative/path/to/your/user/functions');
myFunsDir = strsplit(myFunsPath, filesep);
myFunsDir = myFunsDir{end};
mkdir('C:\MatlabLinks\');
linkPath = ['C:\MatlabLinks\',projectName,'_',myFunsDir];
system(['mklink /J ', '"',linkPath,'" "',myFunsPath,'"']);
addpath(genpath(linkPath));
rmpath(genpath(myFunsPath));

The idea is to create Junction (Symbolic Folder Hardlink) for a folder with your user functions. You may need another method of getting myFunsPath if you don't store your user functions relatively to a project main path. This piece of code will work only in Windows. Make sure you don't add myFunsPath to a search path below in your code, as the trick won't work.

Answer 2

[Julien MORAL]

Hi all, I faced the same issue. For me it was due to the use of unappropriate characters in the Matlab path. Remove the characters with accents (é-è-ä-ü-ö...) if any and it should work. Have a good one

PF

[Abdourahamane DIALLO]

I have an error like this with matlab2013. Except that with matlab2016 I have no error. You can explain to me what is the problem if you plead