Special Notice: Recently Discovered Problem in
CODE V 10.5
If you customize your CODE V interface by creating toolbar or menu items for CODE V macros (either those supplied with CODE V or your own), please be aware of the following situations that might cause CODE V to stop working (crash) when saving a lens using the GUI. The problem may also occur if a macro is run from the Macro dialog box (Tools > Macro Manager menu) with values entered in the Macro Arguments field.
CODE V macros can be written to support an input dialog box. When these macros are run from the GUI, the input dialog is typically launched. For example, following is the input dialog box for the RSIVIEW macro.
There are two ways to suppress the launching of the macro input dialog box:
- For a macro assigned as a toolbar or menu item, the user has left the Prompt for Input control unchecked, as shown in the following figures.
- When running a macro from Macro dialog box (Tools > Macro Manager menu), the launching of the input dialog is overridden if the user enters values in the Macro Arguments field.
In CODE V 10.5, if you run a macro from a toolbar button or menu item that has the Prompt for Input control unchecked, CODE V may stop working if you try to save the lens from the GUI (i.e., File > Save Lens menu or File > Save Lens As menu). CODE V will not have any problems if you close the tabbed output window (TOW) for the problem macro prior to saving.
In CODE V 10.5, if you run a macro from the Macro Manager that supports an input dialog box, but it is not launched because you have entered values in the Macro Arguments field, CODE V may stop working if you try to save the lens from the GUI. CODE V will not have any problems if you close the tabbed output window (TOW) for the problem macro prior to saving.
This problem occurs when the environment (.env) file associated with the lens is written in CODE V 10.5. Lenses saved from the command line (for which no .env file is created) will not have a problem. Environment files created in prior versions of CODE V (e.g., 10.4) are not impacted and can be opened and resaved as long as you have not modified the environment in 10.5 using methods (1) or (2) described above. Also, please note that CODE V will not have problems if the problem macros are run from the command line, even with a TOW command (e.g., TOW IN REFCHECK; TOW IN CV_MACRO:DIST 15 15). This will allow you to save these analyses as part of the lens environment file until the underlying problem is resolved.
We apologize for any inconvenience that this bug may cause. It was inadvertently introduced when we enhanced CODE V to “remember” modified macro dialog inputs as part of a lens environment file (i.e., so that non-default macro inputs are retained when the lens is opened via the GUI in a new session of CODE V).
This problem will be addressed in an upcoming CODE V service release. Please do not hesitate to contact Synopsys’ OSG Customer Support if you have additional questions.
