What does this error mean: CGIR assertion 'index>=0 && index<fSize' failed in 'util_prim/cg_assert.cpp:28'
Show older comments
During Code Generation the following error appears:
CGIR assertion 'index>=0 && index<fSize' failed in 'util_prim/cg_assert.cpp:28'
[ 0] 0xb75d400f /opt/matlab/v26/bin/glnx86/libmwfl.so+00155663 _ZN2fl4diag15stacktrace_base7captureEj+000039
[ 1] 0x994fa6c1 /opt/matlab/v26/bin/glnx86/libmwsimulink.so+09889473
[ 2] 0x97f94370 /opt/matlab/v26/bin/glnx86/libmwcg_ir.so+02343792 _Z23client_assertion_failedPKciS0_+000054
[ 3] 0x97f943a5 /opt/matlab/v26/bin/glnx86/libmwcg_ir.so+02343845 _Z32client_assertion_failed_internalPKc+000047
[ 4] 0x97ef46c5 /opt/matlab/v26/bin/glnx86/libmwcg_ir.so+01689285 _ZNK2CG10StructType9fieldTypeEi+000049
[ 5] 0x96edb8f3 /opt/matlab/v26/bin/glnx86/libmwcgir_construct.so+00370931 _ZN5RTWCG14PropagateSizes13propMemberRefEPN2CG4NodeERNS_9RTWCGTypeE+000171
[ 6] 0x96db760a /opt/matlab/v26/bin/glnx86/libmwrtwcg.so+01136138
[ 7] 0x96da9995 /opt/matlab/v26/bin/glnx86/libmwrtwcg.so+01079701
[ 8] 0x96daaa35 /opt/matlab/v26/bin/glnx86/libmwrtwcg.so+01083957
[ 9] 0x96dab821 /opt/matlab/v26/bin/glnx86/libmwrtwcg.so+01087521 _ZN5RTWCG13DataConnector7replaceEPN2CG7VarExprERNS_12RTWCGFactoryE+000283
[ 10] 0x96dabf7a /opt/matlab/v26/bin/glnx86/libmwrtwcg.so+01089402 _ZN5RTWCG21RTWCGConnectBlockDataEPN2CG3FcnEPNS_10RTWContextE+001750
[ 11] 0x96dac737 /opt/matlab/v26/bin/glnx86/libmwrtwcg.so+01091383 _ZN5RTWCG21RTWCGConnectBlockDataEPN2CG5ScopeEPNS_10RTWContextE+000194
[ 12] 0x96e33e08 /opt/matlab/v26/bin/glnx86/libmwrtwcg.so+01646088 _ZN5RTWCG11RTWFcnConst19OptimizeAndEmitCodeEiPNS_14TLCOutPortInfoERNS_11RTWCGVectorIiEE+002214
[ 13] 0x96dd604f /opt/matlab/v26/bin/glnx86/libmwrtwcg.so+01261647 _ZN5RTWCG11RTWCGModule19OptimizeAndEmitCodeEiPNS_14TLCOutPortInfoE+000141
[ 14] 0x997a5b46 /opt/matlab/v26/bin/glnx86/libmwsimulink.so+12688198
[ 15] 0x997a04ce /opt/matlab/v26/bin/glnx86/libmwsimulink.so+12666062
The model is compiled under Linux 32bit simulink/matlab 2011 with grt target. The same model compiled fine under simulink/matlab 2009 with a different target. The error disappears when I remove a part where a rather big bus-object is used, can this be the problem?
1 Comment
Kaustubha Govind
on 19 Feb 2013
Seems like a bug. Please report this to MathWorks Tech Support.
Answers (3)
Sven
on 19 Feb 2013
Walter Roberson
on 19 Feb 2013
0 votes
The message means that the code detected that the index of something is negative or is beyond the size of what is being indexed. What it is that is being indexed is unknown to me.
Is it possible that the bus-object is more than 2 gigabytes? If so then a "signed" 32 bit index value could appear negative.
Is the 2009 release that you are using a 64 bit release?
Categories
Find more on Schedule Model Components in Help Center and File Exchange
Products
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!