在64位机器上捕获的32位进程的调试转储 [英] Debugging dump of 32-bit process captured on 64-bit machine

问题描述

我最近收到了一个客户的64位崩溃转储。

我们的进程都是32位，但客户的机器正在运行x64 Server 2008。

Visual Studio（2008和2010 Express）告诉我，我必须使用64位版本的 MSVSMON.EXE ，我可以'因为我没有64位机器。

我很确定有一种方法可以在WinDbg中执行此操作，但是我发现WinDbg是敌对的。

有没有办法在32位机器上调试64位转储，最好使用Visual Studio？

解决方案

您需要确保客户使用32位工具（adplus或DebugDiag）来捕获32位进程的崩溃转储。然后，您可以使用32位计算机来调试转储。

http://blogs.msdn.com/b/tess/archive /2010/09/29/capturing-memory-dumps-for-32-bit-processes-on-an-x64-machine.aspx

虽然Isalamon的评论在技术上是正确的，没有人愿意执行，因为堆栈跟踪是可怕的。

让你的客户知道这是必要的，并希望他/她合作。

如果您不熟悉转储分析，Microsoft总是为您而设， http://support.microsoft.com

I recently received a 64-bit crash dump from a customer.
Our processes are all 32-bit, but the customer's machine is running x64 Server 2008.

Visual Studio (both 2008 and 2010 Express) is telling me that I have to use the 64-bit version of MSVSMON.EXE, which I can't because I don't have a 64-bit machine.

I'm pretty sure there's a way to do this in WinDbg, but I find WinDbg to be hostile.

Is there any way to debug a 64-bit dump on a 32-bit machine, preferably using Visual Studio?

解决方案

You need to make sure that customer uses 32 bit tools (adplus or DebugDiag) to capture crash dumps for your 32 bit processes. Then you can use your 32 bit machine to debug the dumps.

http://blogs.msdn.com/b/tess/archive/2010/09/29/capturing-memory-dumps-for-32-bit-processes-on-an-x64-machine.aspx

Though Isalamon's comment is technically correct, nobody would like to execute that as the stack trace is horrible.

Let your customer know that this is necessary, and hope that he/she cooperates.

If you are not familiar with dump analysis, Microsoft is always there for you, http://support.microsoft.com

这篇关于在64位机器上捕获的32位进程的调试转储的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！