Our website uses cookies to enhance your browsing experience.
Accept
to the top
close form

Fill out the form in 2 simple steps below:

Your contact information:

Step 1
Congratulations! This is your promo code!

Desired license type:

Step 2
Team license
Enterprise license
** By clicking this button you agree to our Privacy Policy statement
close form
Request our prices
New License
License Renewal
--Select currency--
USD
EUR
* By clicking this button you agree to our Privacy Policy statement

close form
Free PVS‑Studio license for Microsoft MVP specialists
* By clicking this button you agree to our Privacy Policy statement

close form
To get the licence for your open-source project, please fill out this form
* By clicking this button you agree to our Privacy Policy statement

close form
I am interested to try it on the platforms:
* By clicking this button you agree to our Privacy Policy statement

close form
check circle
Message submitted.

Your message has been sent. We will email you at


If you haven't received our response, please do the following:
check your Spam/Junk folder and click the "Not Spam" button for our message.
This way, you won't miss messages from our team in the future.

>
>
Windows Error Reporting dialog

Windows Error Reporting dialog

Dec 08 2011
Author:

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.

0123-WindowsErrorReporting/image1.png

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.

Popular related articles


Comments (0)

Next comments next comments
close comment form