不支持调试旧格式的crashdumps [英] debugging older format crashdumps is not supported

问题描述

我尝试打开从Windows 7上运行的Windows Server 2008 r2上生成的.dmp文件。 我安装了visual studio 2010 sp1。 每当我尝试打开文件时，都会收到消息："不支持调试旧格式的故障转储
"。

我尝试安装Windows 7的SDK调试工具包这里：
http://www.microsoft.com/download/en/ details.aspx？displaylang = en& id = 8279 （用于Windows 7.1安装程序的Microsoft Windows SDK）。 它没有什么区别。

有人知道打开Windows服务器  2008 r2服务器崩溃转储必须做些什么？

解决方案

据我所知，Visual Studio 2010无法打开内核转储，并且在遇到内容时会输出这种误导性消息。


但是，如果dumpfile没有损坏，来自"Windows调试工具"的windbg.exe应该会成功（根据规范也可以使用"Windows Server 2008 R2"）。 />
或许您可以使用"DumpChk"检查转储文件的有效性，这是一个cmd-line-tool，与windbg位于同一目录中？

用法：

DumpChk [-y SymbolPath] DumpFile

（如果设置了_NT_SYMBOL_PATH环境变量，则不需要SymbolPath。）

带着亲切的问候

p>

I try to open a .dmp file which was generated on a windows server 2008 r2 from my computer which is running on windows 7.  I have visual studio 2010 sp1 installed.  Whenever I try to open the file, I get the message: "debugging older format crashdumps is not supported".

I tried installing the SDK debugging kit for windows 7 found here: http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=8279 (Microsoft Windows SDK for Windows 7.1 Setup).  It does not do a difference.

Anybody knows what must be done to open a windows server 2008 r2 server crash dump?

解决方案

As far as I know, Visual Studio 2010 is incapable of opening kernel-dumps, and will output this misleading message, when confronted with one.
But windbg.exe from "Debugging Tools for Windows", should succeed (according to spec also with "Windows Server 2008 R2"), if dumpfile is not corrupt.
Probably you can check validity of dump-file with "DumpChk", a cmd-line-tool, which lives in the same directory as windbg?
Usage:
DumpChk [-y SymbolPath] DumpFile
(SymbolPath is not required, if _NT_SYMBOL_PATH environment variable is set).

With kind regards

这篇关于不支持调试旧格式的crashdumps的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！