And don’t bother trying to load the 64 bit dbghelp. Additionally, if you need to examine 32 bit procmon stack on a 64 bit OS, you will be out of luck, even if you load the 32 bit dbghelp.dll into the 32 bit instance of Process Monitor it will need to be done on a 32 bit OS if you want symbols to resolve. It’s also worth noting that on a 64 bit OS, Process Explorer and Process Monitor will launch 64 bit processes of themselves, so make sure you also get the 64 bit version of the dbghelp.dll file if you are operating in a mixed environment. Whereas there were no functions in the first image above, now your symbols can resolve: You can also use any number of file extraction utilities, like lessmsi.ĭon’t put the new dbghelp.dll in the system32 folder (it’s protected, anyway)Īnd don’t forget to point to the Microsoft Symbol Server while you’re at it ( ): To do this, open a command shell and type the following command (assuming the msi is on the desktop and you have created a tools folder in C:\Windows): msiexec /a “C:\Document and Settings\ username\Desktop\dbg_x86_ version.msi” /qb TARGETDIR=C:\Windows\Tools Installation
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |