Why does the Simulink Performance Tools 1.3 (R13.0.1) Model Coverage Tool crash when using a single input logic block?

Using the Simulink Performance Tools 1.3 (R13.0.1) Model Coverage Tool with the Modified condition/decision coverage (MC/DC) option turned 'on' results in the following assertion failure:

 covdata = ... cvdata

 id: 111 

 type: TEST_DATA

 test: cvtest object

 rootID: 112 

 checksum: [4x1 struct] 

 startTime: 21-Jul-2003 13:57:00 

 stopTime: 21-Jul-2003 13:57:02 

 metrics: [1x1 struct] 

 failed assertion in L:/build/toolbox/stateflow/src/utils/object.c at line 2755:

 id>0 && id<pool_capacity && object[id]!=NULL

 Stack Trace:

 [0] cv.dll:_dump_c_call_stack_fcn(0x1dfe87cc "id>0 && id<pool_capacity && obje..", 0x1dfe71e8 "L:/build/toolbox/stateflow/src/u..", 2755, 0) + 11

 bytes

 [1] cv.dll:_db_var(0, 541, 0, 0x19e21af8) + 52 bytes

 [2] cv.dll:_message_string(0, 0x01496144, 1024, 2) + 26 bytes 

 [3] cv.dll:_TextOf(52, 1, 0x014969bc, 0) + 1007 bytes 

 [4] cv.dll:_Access_Method(1, 0x014969bc, 5, 0x01496ac0) + 263 bytes

 [5] cv.dll:_try_mexFunction(1, 0x014969bc, 5, 0x01496ac0) + 259 bytes

 [6] cv.dll:_mexFunction(1, 0x014969bc, 5, 0x01496ac0) + 77 bytes

 [7] libmex.dll:_mexRunMexFile(1, 0x014969bc, 5, 0x01496ac0) + 71 bytes

 [8] m_interpreter.dll:_inCallMexFunction(1, 0x014969bc, 5, 0x01496ac0) + 476 bytes

 [9] m_interpreter.dll:_inRunMexFile(1, 0x014969bc, 5, 0x01496ac0) + 121 bytes

 [10] m_interpreter.dll:_inExecMexFile(1, 5, 0x01496ac0, 0x19e976e0) + 82 bytes

 [11] m_interpreter.dll:_inExecFunction(1, 5, 0x01496ac0, 0x19e976e0) + 38 bytes 

 [12] m_interpreter.dll:_inMMexExecute(573, 0x19e976e0, 1, 5) + 533 bytes

 [13] m_interpreter.dll:_inInterPcode(1, 71, 0x1ccd8140, 0) + 1808 bytes 

 [14] m_interpreter.dll:_inColonForBody(0x1ccdd280, 62, 0, 0x3ff00000) + 242 bytes

 [15] m_interpreter.dll:_inForop(0x01497e3c, 2, 2, 592) + 582 bytes

 [snip]

Answer 1

[MathWorks Support Team]

This problem has been fixed in Simulink Performance Tools 1.3.2 (R13SP2). If you are using a previous version, read the following:

This has been verified as a bug in Simulink Performance Tools 1.3 (R13.0.1) in the way that Simulink handles single input logic blocks.

There are currently no known workarounds.