Common error messages

1. Error: simulator exiting because of a previously reported exception
2. Fatal: "C:\Program Files\Cadence\Cierto VCC/include/*.h", line 24: catastrophic error: #error directive: ERROR: Only Mac or Win32 targets supported!
3. Printf doesn't work

Error: simulator exiting because of a previously reported exception

This can mean a number of things and is often accompanied by another error message. If no other error message is shown, it could be because you have external ports in your top-level behaviour.

Fatal: "C:\Program Files\Cadence\Cierto VCC/include/*.h", line 24: catastrophic error: #error directive: ERROR: Only Mac or Win32 targets supported!

When using library functions in VCC, you must either include the appropriate function definition at the top of your file or include the relevant header file. However, the supplied Microsoft header files will only work if you add the following lines before the #include statement:

• #if !defined(_WIN32)
• #define _WIN32
• #endif

Printf doesn't work

To print debugging information to the VCC window, you must use vccPrintPdxDebugInfo. This takes the same arguments as printf and should be defined at the top of your c file as follows:

• int vccPrintPdxDebugInfo(const char *format, ...);

To get messages to appear, you should add "%_START" to the beginning and "%_END_" to the end of the string that you pass to vccPrintPdxDebugInfo.