Debugging an ADRMS-Enabled Application
Debugging an ADRMS-enabled application is not as simple as debugging other types of applications. This is because when an ADRMS application is running inside a debugger and any function that requires the lockbox is called, the application will fail. The application will fail whether or not a breakpoint was set on the secure function. Because of this, you can only start an ADRMS-enabled application inside a debugger mode and debug it until you reach a secure function. As an alternative, you can attach to the running process after the environment object and other secure objects have been created. However, you must then ensure that the application does not call any secure functions while you are debugging, or it will fail.
To allow a more normal debugging process, Microsoft provides a tool, called the lockbox communication proxy (LCP), that acts as a proxy to the actual lockbox. This proxy allows your application to run in a different process than the lockbox. When you use this proxy, you can run your application in debug mode in a relatively normal manner. The LCP is installed with the SDK in the Bin directory.
**RMS Client 1.0 SP2, Windows Vista, Windows Server "Longhorn": **The LCP is not supported. If you attach a debugger and try to step over the DRMInitEnvironment function, you will receive an E_DRM_DEBUGGER_DETECTED error. To debug code following this function, you must set a breakpoint at that code and execute to that point.
For information about how to debug with and without the LCP and what advantages there are to each method, see the following topics:
Debug Message Tracing
The RMS client 1.0 SP1, the RMS client 1.0 SP2, and ADRMS running on Windows Server "Longhorn" or Windows Vista can log debug and troubleshooting messages to the debug output window. By default, debug message tracing is disabled. This option is enabled by setting a value in the registry of the client computer. To enable debug message tracing, add or set the following REG_DWORD registry value.
HKEY_LOCAL_MACHINE
Software
Microsoft
MSDRM
Trace = 1
To disable debug message tracing, set this registry value to zero or remove the value altogether. After this registry value is changed, it will take effect the next time you start your application.