Gflags Notes |
|
Run Tool Open Command Prompt |
Gflags
(with no parameters).You can run Gflags by using its handy dialog box or from the command line. Most features are available in both forms, but the following features are only available from the dialog box:
Debugging settings saved between sessions are stored in the registry. You can use the registry APIs, Regedit.exe, or Reg to query or change these values. The following table lists the types of settings and where they are stored in the registry.
Systemwide debugging values. ("Registry") | HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\GlobalFlag |
Program-specific debugging values. ("Image file") | HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\ImageFileName\GlobalFlag |
Maximum stack trace capture size (maxdepth) | HKLM\System\CurrentControlSet\Control\Session Manager\MaxStackTraceDepth |
Create user mode stack trace database (ust, 0x1000) for an image file | Windows adds the image file name to the value of the USTEnabled registry entry (HKLM\Software\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\USTEnabled). |
Kernel Special Pool Tags | HKLM\System\CurrentControlSet\Control\Session Manager\Memory Management\PoolTag |
Verify Start / Verify End | HKLM\System\CurrentControlSet\Control\Session Manager\Memory Management\PoolTagOverruns. The Verify Start option sets the value to 0. The Verify End option sets the value to 1. |
Debugger for an image file | HKLM\Software\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\ImageFileName\Debugger |