The information in this section is important for understanding how PrimalScript's debugger works, including its requirements and limitations.
The integrated debugger relies on Microsoft Windows components, including the Machine Debug Manager and Process Debugger. These are already available on most Microsoft Windows computers although they may not be properly registered with the operating system. In addition, the debugger is designed to obey Windows' security infrastructure regarding debugging. As a result, the following conditions apply to its use:
•The debugger may need to be used, for the first time on each computer, by a user who has permissions to install and start new services (specifically, the Microsoft Machine Debug Manager which may already exist but which may need to be registered and started). You can see if this will be necessary by examining the list of services installed on the computer; if the Machine Debug Manager service exists and is started, the debugger will not need to register and start it.
•The debugger can only be used by user accounts possessing the Debug Windows user right. This is by design and cannot be circumvented.
•If the debugger is unable to access the Machine Debug Manager service, or if it is unable to obtain Debug permissions from the operating system, it will display an error message.
•Some Microsoft software may create a "debugging" or "debugging-users" group. The user running PrimalScript needs to belong to this group in order for the debugger to work properly.
Some organizations restrict use on their computers by using Group Policy objects, user rights assignment, and security templates. If your organization has done so in such a way that your user account is unable to properly register or start the Machine Debug Manager service, or if your user account does not have the Debug user right, then the debugger will not function. The debugger's inability to function is a consequence of the security decisions your organization has made, and SAPIEN Technologies cannot provide a workaround for your organization's security policies.
These conditions are imposed because the debugger uses many of Windows own services and capabilities to provide advanced debugging features and those services and capabilities are integrated with Windows' own security infrastructure.
See also:
