How to find exception reports for our Validator tools

In an ideal world software would never crash.

In the real world, software crashes. Hopefully infrequently.

Our tools write an exception report when they crash. The user interface writes exception reports, and the software that is injected into your application to monitor it (for memory leaks, code coverage, deadlocks, etc) also writes exception reports.

When the software crashes you will be shown an exception report dialog, but once that dialog has been dismissed how do you find that exception report again?

This article will explain how to find these exception reports.

Finding Exception Reports

Exception reports are stored in c:\users\user-name\AppData\Roaming\Software Verify\product-name\

The name of the exception report is the two letter product code (in lower case), followed by ExceptionLog, then UI.txt or Stub.txt

Exception reports named *ExceptionLogUI.txt describe exceptions in the user interface of a Validator.

Exception reports named *ExceptionLogStub.txt describe exceptions in the application being monitored by a Validator.  These exceptions may be in your code or in Software Verify code.

32 bit exception reports

c:\users\stephen\AppData\Roaming\Software Verify\Coverage Validator x86\cvExceptionLogUI.txt

c:\users\stephen\AppData\Roaming\Software Verify\Coverage Validator x86\cvExceptionLogStub.txt

64 bit exception reports

64 bit exception reports have _x64 appended to the exception report name. 

c:\users\stephen\AppData\Roaming\Software Verify\Coverage Validator x64\cvExceptionLogUI_x64.txt

c:\users\stephen\AppData\Roaming\Software Verify\Coverage Validator x64\cvExceptionLogStub_x64.txt

Full list of exception reports

Bug Validator

c:\users\stephen\AppData\Roaming\Software Verify\Bug Validator x86\bvExceptionLogUI.txt

c:\users\stephen\AppData\Roaming\Software Verify\Bug Validator x86\bvExceptionLogStub.txt

Coverage Validator

c:\users\stephen\AppData\Roaming\Software Verify\Coverage Validator x86\cvExceptionLogUI.txt

c:\users\stephen\AppData\Roaming\Software Verify\Coverage Validator x86\cvExceptionLogStub.txt

c:\users\stephen\AppData\Roaming\Software Verify\Coverage Validator x64\cvExceptionLogUI_x64.txt

c:\users\stephen\AppData\Roaming\Software Verify\Coverage Validator x64\cvExceptionLogStub_x64.txt

Memory Validator

c:\users\stephen\AppData\Roaming\Software Verify\Memory Validator x86\mvExceptionLogUI.txt

c:\users\stephen\AppData\Roaming\Software Verify\Memory Validator x86\mvExceptionLogStub.txt

c:\users\stephen\AppData\Roaming\Software Verify\Memory Validator x64\mvExceptionLogUI_x64.txt

c:\users\stephen\AppData\Roaming\Software Verify\Memory Validator x64\mvExceptionLogStub_x64.txt

Performance Validator

c:\users\stephen\AppData\Roaming\Software Verify\Performance Validator x86\pvExceptionLogUI.txt

c:\users\stephen\AppData\Roaming\Software Verify\Performance Validator x86\pvExceptionLogStub.txt

c:\users\stephen\AppData\Roaming\Software Verify\Performance Validator x64\pvExceptionLogUI_x64.txt

c:\users\stephen\AppData\Roaming\Software Verify\Performance Validator x64\pvExceptionLogStub_x64.txt

Thread Validator

c:\users\stephen\AppData\Roaming\Software Verify\Thread Validator x86\tvExceptionLogUI.txt

c:\users\stephen\AppData\Roaming\Software Verify\Thread Validator x86\tvExceptionLogStub.txt

c:\users\stephen\AppData\Roaming\Software Verify\Thread Validator x64\tvExceptionLogUI_x64.txt

c:\users\stephen\AppData\Roaming\Software Verify\Thread Validator x64\tvExceptionLogStub_x64.txt

Viewing exception reports

The easiest way to view an exception report is from the Validator that relates to the report.

Start the Validator, go to the Help menu and choose Report a crash then one of the options in the submenu.

The options will only be enabled if an exception report is available.

The Report a crash dialog is displayed.

You can view the report and also report it to support@softwareverify. Please include a description of how to reproduce the bug.