Why does the MATLAB Report Generator 2.0 (R14) generate errors during execution in debug mode?

3 views (last 30 days)
I can successfully generate reports in normal or quiet mode from the command line. When I generate reports in debug mode, MATLAB errors out. Also, when I run the Report Generator back in quiet mode, it stays in debug mode and returns a different error. The following are the reproduction steps:
s = report('ch1-tutorial','-debug')
Type these commands at the command prompt:
dbstatus
dbquit
The DBSTATUS command returns
Stop if error.
Stop if caught error.
Stop if warning.
The DBQUIT command returns the following error:
??? Reference to non-existent field 'UseV6PlotAPI'.
Now if I try to run the report in quiet mode, it continues to stay in debug mode.
s = report('ch1-tutorial','-quiet');
The Report Generator outputs the following error:
Caught-error breakpoint was hit in rptgen.report>isSimulink at line 238. The error was:
Error using ==> find_system
Error in specification of object or property name and value pairs.
Executing DBSTATUS returns the same output as in the debug mode. The DBQUIT command returns the following error:
??? Error using ==> find_system
Error in specification of object or property name and value pairs.
To execute the report in quiet mode, you must use DBCLEAR to clear all breakpoints.
dbclear all
s = report('mcurves','-quiet');

Accepted Answer

MathWorks Support Team
MathWorks Support Team on 27 Jun 2009
This bug has been fixed in Release 14 Service Pack 3 (R14SP3). For previous product releases, read below for any possible workarounds:
We have verified that there is a bug in MATLAB Report Generator 2.0 (R14) in the way that it handles the premature termination of the report generation process.
To work around this issue:
1. Download the file, RPTREPAIREXPLORER, attached with this solution
2. Place the file in the MATLAB search path
3. Execute it to repair the Report Explorer interface.
RPTREPAIREXPLORER repairs the Report Explorer user interface if it is stuck in runtime mode. If creation of the report is interrupted using Ctrl+C or debugging commands, the Report Generator cleanup routines are not able to restore the UI to edit mode.
The RPTREPAIREXPLORER command fixes the Report Explorer and makes it editable again. Note that the extent of the repair is not total. The current design of the Report Generator Root object does not allow the library of all components to be rebuilt from this function.
For more information on the RPTREPAIREXPLORER command, type the following in the MATLAB command line once the file is in the MATLAB search path:
help rptrepairexplorer

More Answers (0)

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!