To workaround this, you can copy the dbghelp.dll from another system where the debugging tools have already been installed. Normally, you don’t want to install the debugging tools on user workstations or in situations where time is of the essence–this can be a fairly long installation, require installing other components, and may not work if the OS environmental variable TEMP path happens to be pointing to a location other than the default. Instead, you need the dbghelp.dll from the Windows Debugging Tools to properly resolve symbols, otherwise you will encounter the Process Explorer Warning box when you click the Threads tab in process properties:Īnd the threads will of the process will contain hexadecimal information instead of the functions: By default, Process Explorer and Process Monitor will point to the dbghelp.dll in the windows\system32 folder, but this is a stripped down version and doesn’t support symbol server functionality. The same goes for Process Monitor when viewing the Stack tab in the properties of an operation. Sometimes when you are troubleshooting with Process Explorer, it’s helpful to be able to view functions in threads to isolate a problem. Crashing Config Manager Client & Remote Control Viewer after Windto 1709 Update.The Case of the Dysfunctional Adobe PDF Plugin.
0 kommentar(er)
