Setting Initial Debug Zones
Other versions of this page are also available for the following:
.gif "A checkmark indicates that the information in this topic is relevant for this platform, and that any API listed is also supported on this platform.")
.gif "A checkmark indicates that the information in this topic is relevant for this platform, and that any API listed is also supported on this platform.")
8/27/2008
You can set initial debug zones in the registry on the development workstation or on the target device.
The value set in the registry of the development workstation takes precedence. Thus, if you set the registry value in the registries of both the development workstation and the target device, the value on the development workstation will be enacted. The caller queries the value on the target device only if it cannot reach the development workstation, or if the registry on the development workstation does not contain a value for the module.
- Development workstation registry
Routines on the development workstation read the registry key HKEY_CURRENT_USER\Pegasus\Zones and search for the module name, specified in the Setting Debug Zone Parameters macro.
If the key exists, SetDbgZone uses the stored debug zone mask to update the debug zone name in the DBGPARAM macro. - Target device registry
You can also set the initial debug zones of a specific module on the target device, by modifying the registry of the target device to override the default value of the zone mask.
To set initial debug zones on the target device, create a registry entry in the HKEY_LOCAL_MACHINE\DebugZones registry key with the name of the debug zone and a DWORD value equal to a zone mask.
For example, to turn on the first five debug zones for a module named VoIPPhone, create a VoIPPhone entry with DWORD value 0x001F.
When you set the registry value on the target device, use the same registry value that you use on the development workstation.