Stay tuned for other articles of interest as I work through the book. In various places on the Internet and in my hands-on testing. It is pretty in-depth for this task, and I hope educational, showing many things all in one place that I found Because the place Microsoft puts it has changed, and manyĪrticles about Process Explorer symbols do not address the Dbghelp.dll path, it took me a while to get this right. The problem was getting pointed to the right dbghelp.dll file. The Microsoft Symbol Server path and Symbols path format has not changed form in quite some time. So, that might be a potential problem to watch out for. When I did start it with Administrator privileges, I had to reconfigure the Symbol Configuration - it had gone back to the initial configuration. It populated the symbol cache, so it was working for other programs.Īlso, a gotcha: I noticed when I set up the Symbols Configuration in Process Explorer when not started with Administrator privileges, However, the environment variable setup did not seem to work for Process Explorer, but when I opened a debug session in Visual Studio, Final TipsĪs discussed here, setting up a Symbols Path environment variable _NT_SYMBOL_PATH, which uses the sameįormat as above, can be very useful for Windows debuggers (WinDbg, Visual Studio, etc.) in certain situations. In a process’ properties dialogue box for an appropriate amount of time, something is wrong. ( d:\symbols in my case) with file explorer and see if it contains files and folders. You can also click the Stack button to see a stack trace:Īnother way to verify explicitly that the symbol server functionality is working is to just go look at the local cache folder In my experience, it has never taken more than 2-3 minutes to start going, but that can seem like a long time when just staring at the dialog box. Let me emphasize that: be very patient! It may take a while until they start filling in, and you may think it is broken prematurely. The symbols will automatically fill in as they are acquired. Note that, especially at first, there may be a delay as the symbols are acquired from the Microsoft symbol server. You can either paste the following path into its input box: Now, you need to point to the right dbghelp.dll file. Or, install only the Debugging Tools for Windows by installing the SDK but selecting Debugging Tools for Windows and deselecting everything else.Either install the Software Development Kit, including selecting the Debugging Tools for Windows.This immediately preceding link explains how to install those tools for Windows 10. If you have not already, you will need to get a copy of the dgbhelp.dll that comes with the Debugging Tools for Windows. You will need to do some work to get the right version of the dll and point to it. The initial value for that path shown above points to a version of that dll that will not work. Configuring the Dbghelp.dll Pathįirst, lets tackle the dgbhelp.dll path. Note that the Symbols path is empty, and the default path to dbghelp.dll is in the C:\Windows\System32 subdirectory, which will not work. This is what the dialog box looks like the first time you use it: Detailed Instructions and Tipsįirst, open up the Options | Configure Symbols. It here for the benefit of others and give some detailed insights into how to know whether it is truly working or not. I finally made it work, and came to understand why it was not working, so I thought I would explain I did not see the screenshot, just the link. Path, and other articles on the web were also outdated or did not give the windbg.dll path at all. His screenshot was correct, but the link he gave for information had an old windbg.dll However, I was not having much success getting it to work. The book uses Sysinternals Process Explorer application heavily and discusses how to enable debugging symbols downloads via the Microsoft symbol server to enable resolution of raw address offsets in executables to symbolic names, for instance, in the Threads tab of a process’s Properties dialogue box or in stack traces. I am following along in Windows Internals, Part 1, Edition 7 by Mark Russinovich, et. NOTE: The Dbghelp.dll path is different from the paths I have seen in older articles, The Debugging Tools for Windows installed after the WDK too. This is my setup, and works for me, with the Windows Driver Kit (WDK) installed as well as the Software Development Kit (SDK) with You can call it whatever you want, and put it My C: drive is short on space, and the the local symbols cache can get very big, many gigabytes. In the picture above, I show the path to the local symbols cache (between the asterisks in the Symbols path) on the D: drive.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |