blocks|key|3006270|text|在.NET+4中将CLR运行时dll重命名为clr.dll。因此，为了加载正确版本的.NET，您需要调整您的.loadby命令。也就是说。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3006271|.loadby+sos+clr|code-block|syntax|javascript|3006272|此外，如果你使用的是64位，你也应该安装32位版本的Debugging+Tools+for+Windows，以便调试32位应用程序。它们是并排安装的，所以在同一台机器上同时安装32位和64位版本是没有问题的。|3006273|我建议不要复制SOS.dll。SOS需要与框架的确切版本相匹配，所以只要您使用.loadby从框架目录加载它，就一切就绪。|3006274|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/^0|M|7|1I|7|0|0|Q|R|0|0|13|7|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]|$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|11|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|12|8|@]|D|@$9|13|A|14|1|15]]|E|$]]|$1|M|3|N|5|6|7|16|8|@$9|17|A|18|B|C]]|D|@]|E|$]]|$1|O|3|-4|5|6|7|19|8|@]|D|@]|E|$]]]|P|$Q|$5|R|S|T|E|$U|V]]]]

The CLR runtime dll was renamed to <code>clr.dll</code> with .NET 4. So in order to load the correct version of SOS you need to adjust your <code>.loadby</code> command. I.e.

<pre><code>.loadby sos clr
</code></pre>

Also, if you're on 64 bit, you should install the 32 bit version of <a href="https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/" rel="noreferrer">Debugging Tools for Windows</a> as well in order to debug 32 bit apps. They install side-by-side, so there's no problem in having both the 32 bit and the 64 bit version on the same machine. 

I would advice against copying SOS.dll. SOS needs to match the exact version of the framework, so as long as you load it from the framework directory using <code>.loadby</code>, you're all set.

blocks|key|3006338|text|WinDbg命令'g‘表示继续|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3006339|因为你正在打开一个转储文件，所以没有办法“继续”，它只包含进程内存。|3006340|因此，消息“No+runnable+debuggees+error+in+'g‘”在您的情况下是合乎逻辑的，因为进程没有运行。|3006341|关于加载正确版本的SOS，请根据.NET版本使用以下命令。|3006342|.NET+4和更高版本的+.loadby+sos|offset|length|style|BOLD|3006343|.NET+3.5和2个+.loadby+sos+mscorwks|3006344|.NET+1.0和1.1+.load+clr10\sos|3006345|entityMap^0|0|0|0|0|0|C|0|0|B|0|0|C|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|X|8|@$J|Y|K|Z|L|M]]|9|@]|A|$]]|$1|N|3|O|5|6|7|10|8|@$J|11|K|12|L|M]]|9|@]|A|$]]|$1|P|3|Q|5|6|7|13|8|@$J|14|K|15|L|M]]|9|@]|A|$]]|$1|R|3|-4|5|6|7|16|8|@]|9|@]|A|$]]]|S|$]]

The WinDbg command 'g' means [Continue]

Since you're opening a dump-file there is no way to 'continue', it only contains the process memory.

So the message " No runnable debuggees error in 'g' " is logical in your case since the process is not running.

Concerning loading the correct version of SOS use the following command depending on the .NET version.

.NET 4 and higher .loadby sos 

.NET 3.5 and 2
.loadby sos mscorwks

.NET 1.0 and 1.1
.load clr10\sos

blocks|key|3006357|text|刚刚在加载SOS时遇到了类似的问题，并得到“无法找到指定的模块”。想出了一个不同的解决方案，所以如果这里的解决方案对你没有帮助，试试这个：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3006358|.loadby+sos+clr+-+specified+module+could+not+be+found|offset|length|3006359|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/38874734/loadby-sos-clr-specified-module-could-not-be-found/38877753#38877753^0|0|0|1H|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

Just came across a similar issue loading SOS and was getting "specified module could not be found". Came up with a different solution so if the solutions here don't help you, try this out:

<a href="https://stackoverflow.com/questions/38874734/loadby-sos-clr-specified-module-could-not-be-found/38877753#38877753">.loadby sos clr - specified module could not be found</a>

blocks|key|286881|text|上面的答案需要改进，因为随着时间的推移，事情变得更容易处理sos加载。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|286882|JOHN+ROBBINS在它周围有很好的article，看到微软的符号服务器被配置在符号文件路径中并运行!analyze+-v+on+windbg提示，这将做的技巧它将下载相关的article文件。为了验证，在提示符后运行.chain，您将看到已加载的dll。|offset|length|286883|entityMap|0|LINK|mutability|MUTABLE|url|http://www.wintellect.com/devcenter/jrobbins/automatically-load-the-right-sos-for-the-minidump|1^0|0|K|7|0|2H|7|1|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@$D|Q|E|R|1|S]|$D|T|E|U|1|V]]|A|$]]|$1|F|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]|N|$5|I|J|K|A|$L|M]]]]

Answers above need improvement, since over the course of time things has been easier to handle sos loading.

JOHN ROBBINS has nice <a href="http://www.wintellect.com/devcenter/jrobbins/automatically-load-the-right-sos-for-the-minidump" rel="nofollow noreferrer">article</a> around it, See that Microsoft symbol servers are configured in symbol file path and run !analyze -v on windbg prompt, this will do the trick it will download relevant sos files. 
To verify run .chain on the prompt and you will see the loaded dll.

Background: I'm new to WinDbg and trying to get it running for the first time. I want to examine a memory dump I took from a running ASP.NET 4 site hosted in IIS 7 on Windows Server 2008 (x86) and downloaded to my local machine.
I installed the <a href="http://www.microsoft.com/whdc/devtools/debugging/default.mspx" rel="noreferrer">debugging tools</a> and launched WinDbg for the first time, opening the crash dump. I went to File | Symbol File Path and set the path to <code>*srv*c:\symbols*http://msdl.microsoft.com/download/symbols*</code> and waited for all the symbols to load.
When trying to load SOS, I ran into problems. First, I tried the following command...
<pre><code>.loadby sos mscorwks
</code></pre>
...and received the response <code>Unable to find module 'mscorwks'</code>.
After scouring the web, I tried to load mscorwks by executing the following command...
<pre><code>sxe ld mscorwks.dll
g
</code></pre>
...and received the response &quot;No runnable debuggees error in 'g'&quot;
I copied SOS.dll (from C:\Windows\Microsoft.NET\Framework\v4.0.30319) into the WinDbg directory, then tried...
<pre><code>.load sos
</code></pre>
...and received the error...
<pre><code>The call to LoadLibrary(sos) failed, Win32 error 0n193
 &quot;%1 is not a valid Win32 application.&quot;
Please check your debugger configuration and/or network access.
</code></pre>
I'm not quite sure how to proceed. I just want to load SOS and dig around this dump file. Any help would be greatly appreciated.
Fyi...I am trying to open the dump file on a 64-bit version of Windows 7 with the 64-bit version of Windbg.

Unable to load SOS in WinDbg

Windows Server

服务器

Windows

背景:我是WinDbg的新手，并且第一次尝试让它运行起来。我想检查从Windows Server2008 (x86)上的IIS7中运行的ASP.NET 4站点获取并下载到我的本地计算机上的内存转储。我第一次安装了并启动了WinDbg，打开了崩溃转储。我转到文件|符号文件路径，将路径设置为*srv*c:\symbols*...

问无法在WinDbg中加载SOS
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问无法在WinDbg中加载SOSEN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问无法在WinDbg中加载SOS
EN