.quit_lock (Prevent Accidental Quit)
The .quit_lock command sets a password to prevent you from accidentally ending the debugging session.
.quit_lock /s NewPassword
.quit_lock /q Password
.quit_lock
Parameters
/s **** NewPassword
Prevents the debugging session from ending and stores NewPassword. You cannot end the debugger session until you use the .quit_lock /q command together with this same password. NewPassword can be any string. If it contains spaces, you must enclose NewPassword in quotation marks.
/q **** Password
Enables the debugging session to end. Password must match the password that you set with the .quit_lock /s command.
Environment
| Item | Description |
|---|---|
| Modes | User mode, kernel mode |
| Targets | Live, crash dump |
| Platforms | All |
Remarks
Without parameters, .quit_lock displays the current lock status, including the full text of the password.
You can repeat the .quit_lock /s command to change an existing password.
When you use .quit_lock /q, the lock is removed. This command does not close the debugger. Instead, the command only enables you to exit the session in the typical manner when you want to.
Note The password is not "secret". Any remote user who is attached to the debugging session can use .quit_lock to determine the password. The purpose of this command is to prevent accidental use of the q (Quit) command. This command is especially useful if restarting the debugging session might be difficult (for example, during remote debugging).
You cannot use the .quit_lock /s command in Secure Mode. If you use this command before Secure Mode is activated, the password protection remains, but you cannot change or remove the password.
Important
There are important security considerations when using remote debugging. For more information, including information on enabling secure mode, see Security Considerations for Windows Debugging Tools.