在32位计算机上通过64位转储在WinDbg中丢失 [英] Lost in WinDbg with 64-bit dump on 32-bit machine

查看:93
本文介绍了在32位计算机上通过64位转储在WinDbg中丢失的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我是WinDbg的新手,是从64位Windows 2008 Server的WER ReportQueue文件夹中获得此转储的。
我需要检查转储,并要在安装了Windows调试工具包的开发人员计算机上进行检查。
当我尝试加载SOS时,遇到了以下我从未见过的错误:

  0:035> ; .loadby sos mscorwks 
对LoadLibrary(C:\Windows\Microsoft.NET\Framework64\v2.0.50727\sos)的调用失败,Win32错误126
指定的模块无法被发现。
请检查您的调试器配置和/或网络访问。

我的机器运行的是32位Windows 7,显然没有Framework64文件夹。 / p>

我需要一些建议,以正确的方向向我指出。如果要检查32位计算机上64位进程的转储,该怎么办?



预先表示感谢!

解决方案

如果要分析64位进程转储,则需要在64位计算机上运行调试器的64位版本。可以在32位和64位计算机上分析32位进程的转储。因此,如果您确定转储来自64位进程,则需要在64位计算机上对其进行分析。


I'm a newbie with WinDbg and got this dump from the WER ReportQueue folder on a 64-bit Windows 2008 Server. I need to examine the dump and want to do so on my developer machine on which I've installed the Debugging Tools for Windows package. When I try to load SOS I got the following error which I've never seen before:

0:035> .loadby sos mscorwks
The call to LoadLibrary(C:\Windows\Microsoft.NET\Framework64\v2.0.50727\sos) failed, Win32 error 126
    "The specified module could not be found."
Please check your debugger configuration and/or network access.

My machine is running 32-bit Windows 7, which obviously doesn't have the Framework64 folder.

I need some advice pointing me in the right direction here. What do I need to do if I want to examine the dump from a 64-bit process on a 32-bit machine? Is it possible to do this?

Big thanks in advance!

解决方案

If you want to analyze a 64-bit process dump then you need to run the 64 bit version version of the debugger on a 64-bit machine. A dump from 32-bit process can be analyzed on 32-bit and 64-bit machine. So if you are sure the dump is from 64-bit process, it needs to be analyzed on 64-bit machine.

这篇关于在32位计算机上通过64位转储在WinDbg中丢失的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆