windbg

问题 For some reason, I cannot run any commands once I load psscor4. I have downloaded x64 of psscor4 from MS website and put it in same folder where windbg is. Before loading psscor4, I can run sos commands fine without any problem. 0:003> .loadby sos clr 0:003> lmvm clr start end module name 00007ffa`35630000 00007ffa`35fc8000 clr (deferred) Image path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll Image name: clr.dll Timestamp: Wed Nov 27 19:25:30 2013 (52968D7A) CheckSum: 00996ED8

问题 I made a dump (using -ma option and a trigger for high CPU in procdump.exe) of a .NET process and I want to see the clues in a running thread about what my code was doing. I get this: *** procdump -ma -c 65 -s 2 -n 3 service.exe *** Process exceeded 65% CPU for 2 seconds. Thread consuming CPU: 4396 (0x112c)' The indicated thread was executing that at the dump time: 0:022> k ChildEBP RetAddr WARNING: Frame IP not in any known module. Following frames may be wrong. 0990f104 040666ab 0x40656f8

问题 I'm using WinDBG occasionally to analyze problems in production environment, where VS cannot be installed. There's no doubt it's an extremely powerful tool, but using it is a bit annoying. Even though the product is frequently updated, its GUI goes back to the Win95 days or so, and its usability is accordingly. Having to fight the GUI to layout the windows the way I want, and having to remember all those textual commands, is just quite low a standard for a modern desktop application. AFAIK,

问题 The Question There are plenty of manual ways to make WinDBG find mscordacwks.dll without a symbol store (putting the file in the path somewhere, putting it in the same folder as windbg.exe, putting it in my Framework\v folder, specifying the path in WinDBG using .cordll -lp c:\dacFolder , etc.), but they all only fix it for me . I need to fix it more generally for everyone who uses my symbol store . The possible solutions I can imagine are: WinDBG be made to check the symbol store using

问题 here is what I'm trying to solve. I have a crash dump from Google Chrome. I open windbg and say File -> Symbol File Path: "SRV*c:\code\symbols*http://msdl.microsoft.com/download/symbols;SRV*c:\code\symbols*https://chromium-browser-symsrv.commondatastorage.googleapis.com" I guess this looks for the debugging symbols from let to right and should finally grab them from google then. I copied that from http://www.chromium.org/developers/how-tos/debugging. I drag and drop the crash dump into windbg

问题 I'm working on a dump, which I try to investigate, using PYKD technology. The result of the x /2 *!*``vtable' (just one backtick) contains the following result: 745293b8 mfc110u!CPtrList::`vftable' However, when I try to get more information about this class, I get a "symbol not found" exception: Python source code: dprintln("name=[%s]" % type_stats.name) if not type_stats.name in typesize_by_type: try: type_info = typeInfo(type_stats.name) except Exception, e: dprintln("text=[%s]" % (str(e))

问题 Is there a way to trigger a garbage collection in a .NET process from another process or from inside WinDBG? There are the Managed Debugging Assistants that force a collection as you move across a native/managed boundary, and AQTime seems to have button that suggests it does this, but I can't find any documentation on how to do it. 回答1: Well... there's the immediate window. If you have the luxury of attaching to the process, I supposed you could manually GC.Collect in the immediate window.

问题 I am using sos.dll and windbg to anayze a w3wp.exe dump. There is a high number of .Net CLR exceptions thrown per/sec shown in perfmon and i am trying to investigate this. I tried doing a !dumpheap -stat -type Exception. But does this show the exceptions that were thrown at the instance i took the dump or does this show all the exception object instances that were created? Exception object instances may be created without being thrown. Is there a way to just get the exceptions that were

问题 I noticed the EBP pointer on top of the stack frame is not quite right when a bare simple MFC's main application object is instantiated and this happens only in release build. Here is the code. CMDIDemoApp::CMDIDemoApp() { // support Restart Manager m_dwRestartManagerSupportFlags = AFX_RESTART_MANAGER_SUPPORT_ALL_ASPECTS; #ifdef _MANAGED // If the application is built using Common Language Runtime support (/clr): // 1) This additional setting is needed for Restart Manager support to work