As with any other native Windows program, there exists a possibility of an unhandled exception being raised during the operation of PVS-Studio analyzer (the PVS-Studio.exe process in particular), this can be because of the call stack overflow for example. The Windows family operating systems starting with Windows Vista would generate a special emergency shutdown dialog in case of an unhandled exception allowing you to debug or close such crashing program.
Figure 1 —Error Reporting Dialog
But the process causing the appearance of such a dialog will not be terminated by the operation system until the user closes this dialog manually. Such a behavior potentially could be undesirable. For instance, while launching the analyzer in automatic batch mode for a large amount of files to be verified from within the makefile-based build system, the appearance of this dialog will result in a complete halt of the entire build system, which in turn will require a user interaction for a resumption of the building process.
To prevent the generation of Windows Error Reporting dialog you should modify the value of HKEY_CURRENT_USER\Software\ Microsoft\Windows\Windows Error Reporting\DontShowUI registry key to 1. However, we discourage this, as such behavior will make it impossible to identify and resolve any potential issues with the analyzer and any other software on your system.
Many programmers think that the more error messages a static code analyzer produces, the better. It would be true if all the messages hit the bull's eye, as they say. But this is impossible: the same warnings may be considered both true and false by different programmers depending on the project type. There is also one more important and interesting ...