For more information, see How to: Install and Uninstall Services. To debug a serviceīuild your service in the Debug configuration. If you're debugging a system process or want to have symbols for system calls in your services, you should add the Microsoft Symbol Servers. See Specify Symbol (.pdb) and Source Files in the Visual Studio Debugger. If you are debugging a service that you didn't build, you should first find symbols for the service and make sure they can be found by the debugger. If you are debugging a service that you built in Visual Studio, the symbol files (.pdb files) are in the same folder as the executable or library, and the debugger loads them automatically.
To get meaningful information for debugging, the Visual Studio debugger needs to find symbol files for the binaries that are being debugged. This article covers debugging a service that's running on the local computer, but you can also debug Windows Services that are running on a remote computer. You can later remove this dummy service after debugging is successful. You can use the Services Control Manager to start, stop, pause and continue your service, thus hitting the breakpoints you've set. Once you exit the dialog box you use to attach to the process, you are effectively in debug mode. That is, if your service is running when you begin debugging, it is still technically in the Started state as you debug it, but its processing has been suspended.Īfter attaching to the process, you can set breakpoints and use these to debug your code. The attachment process interrupts the current functioning of your service it doesn't actually stop or pause the service's processing. You can attach the debugger only to a running service. For example, if you attach to the WinLogon process and then stop debugging, the system will halt because it can't operate without WinLogon.
You should not attach to a process unless you know what the process is and understand the consequences of attaching to and possibly killing that process.
0 kommentar(er)
