无法读取 windbg 中的故障转储 [英] Unable to read crash dump in windbg

问题描述

我的程序中出现了 stackoverflow 异常，该异常可能源自第三方库 microsoft.sharepoint.client.runtime.dll.

I have been getting a stackoverflow exception in my program which may be originating from a thirdparty libary, microsoft.sharepoint.client.runtime.dll.

使用 adplus 创建故障转储，我面临的问题是，当我在 Windbg 中打开它时，我很难从中获取任何信息.这是我得到的回应:

Using adplus to create the crash dump, I'm facing the problem that I'm struggling to get any information from it when i open it in windbg. This is what I get as a response:

> 0:000> .restart /f

Loading Dump File [C:\symbols\FULLDUMP_FirstChance_epr_Process_Shut_Down_DocumentumMigrator.exe__0234_2011-11-17_15-19-59-426_0d80.dmp]
User Mini Dump File with Full Memory: Only application data is available

Comment: 'FirstChance_epr_Process_Shut_Down'
Symbol search path is: C:\symbols
Executable search path is: 
Windows 7 Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: Server, suite: Enterprise TerminalServer SingleUserTS
Machine Name:
Debug session time: Thu Nov 17 15:19:59.000 2011 (UTC + 2:00)
System Uptime: 2 days 2:44:48.177
Process Uptime: 0 days 0:13:05.000
.........................................WARNING: rsaenh overlaps cryptsp
.................WARNING: rasman overlaps apphelp
......
..WARNING: webio overlaps winhttp
.WARNING: credssp overlaps mswsock
.WARNING: IPHLPAPI overlaps mswsock
.WARNING: winnsi overlaps mswsock
............
wow64cpu!CpupSyscallStub+0x9:
00000000`74e42e09 c3              ret

关于如何从转储中获取更多信息，或如何使用它来查找我的计算器溢出错误发生位置的任何想法?

Any ideas as to how i can get more information from the dump, or how to use it to find where my stackoverflow error is occuring?

推荐答案

您面临的问题是进程是 32 位的，但您在 64 位上运行，因此您的转储是 64 位转储.要使用转储，您必须运行以下命令:

The problem you are facing is that the process is 32-bit, but you are running on 64-bit, therefore your dump is a 64-bit dump. To make use of the dump you have to run the following commands:

.load wow64exts
.effmach x86
!analyze -v

最后一个命令应该会给你一个有意义的堆栈跟踪.

The last command should give you a meaningful stack trace.

这篇关于无法读取 windbg 中的故障转储的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！