Why do I receive an error during the TLC portion of code generation using the Real-Time Workshop?
2 views (last 30 days)
Show older comments
I am allocating a large amount of text to the TLC buffer. During the code generation I receive an error or a segmentation violation. The error looks like the following:
Output file prmBuff opened with %openfile was not closed
Or, I receive a blank error message. The stack trace of the segmentation violations looks like:
Stack Trace:
[0] tlc_new.dll:_rtw_bufio_write(0x0a7e9988, 0x5b470044 "LINE NUMBER: 0 ITERATION N..", 0x20000000, 0x11bfba74) + 100 bytes
[1] tlc_new.dll:_rtw_output(0x0a7e9988, 0x5b470044 "LINE NUMBER: 0 ITERATION N..", 0x11bfba74, 0x1999f540) + 322 bytes
[2] tlc_new.dll:_rtw_output_value_private(0x0a7e9988, 0, 0x5b470030, 0) + 1106 bytes
[3] tlc_new.dll:_rtw_output_value_private(0x0a7e9988, 0x0a9ba190, 0x0a9ba190, 1) + 1056 bytes
[4] tlc_new.dll:_rtw_output_value(0x0a7e9988, 0x0a9ba190, 1, 0x0a7ebd6c) + 21 bytes
[5] tlc_new.dll:_tlc_output_value(0x0a7e9988, 0x1b330208, 0x1b330224, 0x1b330228) + 30 bytes
[6] tlc_new.dll:_rtw_interp_simple_primitive(0x0a7ebd6c, 0x1a1b68b0, 0x1b330208, 0x1b330224) + 25 bytes
[7] ir_interp.dll:_in_interpret(0x0a7ebdd0, 0x0a7ebdd0, 0x1a3b00d8, 0) + 2150 bytes
[8] ir_interp.dll:_in_interpret_start(0x0a7ebdd0, 0x1a3b00d8, 0, 0x0a9ba570) + 68 bytes
[snip]
Or:
[0] libmwm_ir.so:mps_compare_constant(0x082ce098, 0xbfff6ce8,0x083e9308, 0x40035906) + 201 bytes
[1] libut.so:ut_ghash_query_remove_element(0x082ce1a0, 0xbfff6ce8, 0, 0x40036610) + 102 bytes
[2] libut.so:ut_ghash_remove_element(0x082ce1a0, 0xbfff6ce8, 0x08243c48, 0x402d1656) + 35 bytes
[3] libmwm_ir.so:mps_delete_constant(0x082ce098, 0x50329010, 0xbfff6d18,0x4ed2b12e) + 118 bytes
[4] tlc_new.mexglx:rtw_scope_clear(0x082cdbe0, 0x0823b244, 0xbfff6d5c, 0x4ed2d94a) + 193 bytes
[snip]
Accepted Answer
MathWorks Support Team
on 27 Jun 2009
This bug has been fixed for Release 14 (R14). For previous releases, please read below for any possible workarounds:
This has been verified as a bug in The Real-Time Workshop 4.1 (R12.1) and later versions in the way that the Target Language Compiler handles large buffer sizes.
There are currently no known workarounds.
0 Comments
More Answers (0)
See Also
Categories
Find more on Simulink Coder 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!