.loadby sos clr - specified module could not be found

前端 未结 3 391
盖世英雄少女心
盖世英雄少女心 2020-12-29 17:44

I am trying to get to the bottom of what the CLR exception that is in my dump file but I am having an issue trying to execute:



        
相关标签:
3条回答
  • 2020-12-29 18:01

    WER generated 2 files in my case: triagedump.dmp (2 MiB) and memory.hdmp (400 MiB).

    triagedump.dmp contains only exception info, SOS does not work with it.

    memory.hdmp is minidump, SOS loaded CLR successfully.

    0 讨论(0)
  • 2020-12-29 18:08

    Figured out the answer using what I learned from @Thomas Weller's questions. So apparently the "Symbol File Path" in File -> Symbol File Path gets cleared every time you close WinDbg and without it .loadby sos clr produces the error that I got. The "Symbol File Path" in File -> Symbol File Path must have an entry in there like: srv*C:\windbg\websymbols (and of course the directory must exist).

    When you open a crash dump it should have the following output (Notice the line: Symbol search path is: srv*C:\windbg\websymbols):

    Microsoft (R) Windows Debugger Version 10.0.14321.1024 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\XXXXXX\Desktop\AppCrash_XXXXXXXXXXXXX_d4c077fd50acba44bd2aceb966fe5424b98f3e_cab_9eb7d2f5\WERC4D4.tmp.hdmp]
    User Mini Dump File: Only registers, stack and portions of memory are available
    
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       srv*C:\windbg\websymbols
    Symbol search path is: srv*C:\windbg\websymbols
    Executable search path is: 
    Windows 7 Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: Server, suite: TerminalServer SingleUserTS
    Machine Name:
    Debug session time: Tue Aug  9 02:05:43.000 2016 (UTC - 4:00)
    System Uptime: 79 days 17:08:17.121
    Process Uptime: 0 days 0:00:06.000
    

    On the other hand, this is what I had previously and this means you forgot to set the "Symbol File Path" (Notice the line Symbol search path is: srv*)

    Microsoft (R) Windows Debugger Version 10.0.14321.1024 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\XXXXXX\Desktop\AppCrash_XXXXXXXXXXXXX_d4c077fd50acba44bd2aceb966fe5424b98f3e_cab_9eb7d2f5\WERC4D4.tmp.hdmp]
    User Mini Dump File: Only registers, stack and portions of memory are available
    
    Symbol search path is: srv*
    Executable search path is: 
    Windows 7 Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: Server, suite: TerminalServer SingleUserTS
    Machine Name:
    Debug session time: Tue Aug  9 02:05:43.000 2016 (UTC - 4:00)
    System Uptime: 79 days 17:08:17.121
    Process Uptime: 0 days 0:00:06.000
    
    0 讨论(0)
  • 2020-12-29 18:17

    As mentioned by @Thomas Weller this workaround works for now:

    .load C:\Windows\Microsoft.NET\Framework64\v4.0.30319\SOS.dll
    
    0 讨论(0)
提交回复
热议问题