Enter the corresponding value data (1) for each value, selecting its Base (2) if necessary, and click OK (3).Once you have created the above values, right-click (1) on them and select Modify (2) to set their value data, still according to the table of the previous step.This value is used only when DumpType is set to 0. When the maximum value is exceeded, the oldest dump file in the folder will be replaced with the new dump file. The maximum number of dump files in the folder. The path where the dump files are going to be stored. Table 1: Registry Values for Collecting Crash Dumps Under the MyApplication.exe key, add the values on the table below by right-clicking on the right pane of the Registry Editor and selecting New (1) followed by the corresponding value type (2).For example, HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Windows Error Reporting\LocalDumps\MyApplication.exe (1). Following the same steps, create another new key for your application under the LocalDumps key.Name the key LocalDumps (1) and press Enter.If it’s not present already, add the LocalDumps key by right-clicking (1) on the Windows Error Reporting key and selecting New (2) > Key (3).Navigate to the Windows Error Reporting (1) key under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting.Open the Registry Editor by typing “ regedit” (1) in the Start Menu and pressing Enter. Since this feature is not enabled by default, its activation requires administrator privileges. Windows Error Reporting (WER) can be configured to collect full dumps from application crashes, and store them locally on your machine. On windows, you can configure your system to automatically collect crash dumps of your applications and use Visual Studio or WinDBG to debug them.Ĭollecting Crash Dumps Configuring Windows Error Reporting
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |