Plug-in exception handling / crash reporting

 

Note: Plug-in crashes should always be first reported to the manufacturer's support channels to allow them to diagnose these issues.

Sonar’s integrated error reporting helps you with diagnosing plug-in or application crashes:

Sonar distinguishes between plug-in and application crashes and will list the plug-in name where available in the crash dialog.

For easy reporting, the crash dump file when generated is displayed as a hyperlink allowing you to click to open the location of the file.

The application also intercepts and reports errors instead of silently shutting down. You will get a dump file where possible and the ability to save your current work in these scenarios.

Additionally, when applicable, the crash dialog allows you to continue after a crash. Please note that the behavior after resuming is not guaranteed and is provided as a last resort to access project information when a crash occurs. It should only be used in cases where the crash is known to be continuable.

To specify the error detection sensitivity, add the following variable in Cakewalk.ini (Edit > Preferences > File - Initialization File):

ExceptionHandlingSeverity=<value>

Valid values for this setting are:

1 = Unhandled errors are caught (default)

3 = All access violations are detected and unhandled exceptions are caught

5 = Unhandled errors and heap corruption is detected

7 = Unhandled errors, all access violations and heap corruption errors are caught (this is the strictest error detection mode)

The sensitivity value defaults to 1 but can changed to 7 make it catch even more plug-in errors.

To revert to the default value, delete the ExceptionHandlingSeverity variable.

 

See:

Initialization files

Cakewalk.ini

Frequently asked questions