如何解释此崩溃转储 [英] How to interpret this crash dump

查看:535
本文介绍了如何解释此崩溃转储的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我们遇到了iis托管的特定网站的问题,我没有从事件日志中获取太多信息。我使用这些低级别的'原始'诊断工具有点超出了我的联盟,如果我在错误的树上咆哮,我就不会这样了(在这种情况下请告诉我 - 例如IIS刚刚坏掉)或者我是不是m按照正确的路径尝试找到问题。

We've been encountering an issue with a particular website hosted in iis for which I've not managed to get much information from the event log. I'm a bit out of my league with these low level 'raw' diagnostic tools and I'm not if I'm barking up the wrong tree (in which case please tell me - e.g IIS is just broken) or whether I'm following the correct paths to try and locate the issue.


服务应用程序池'MyWebsite'的进程与Windows发生致命的通信错误流程激活服务。进程ID为'4372'。数据字段包含错误编号。

A process serving application pool 'MyWebsite' suffered a fatal communication error with the Windows Process Activation Service. The process id was '4372'. The data field contains the error number.

运行DebugView打开我遇到问题时可靠地看到这些行

Running with DebugView open I reliably see these lines when I encounter an issue


[5904] 4692 iisutil!ReadMultiStringParameterValueFromAnyService [helpfunc.cxx @ 490]:Inetinfo:读取注册表值失败
[5904]

错误(80070002):系统找不到指定的文件。

[5904] 4692 iisutil!ReadMultiStringParameterValueFromAnyService [helpfunc.cxx @ 490]:Inetinfo: Failed reading registry value [5904]
Error(80070002): The system cannot find the file specified.

因此我尝试安装DebugDiag并查找任何异常,这会为我创建一些完整的转储。一旦我分析了它们,我就会在下面显示另一端报告,但我不确定如何进一步分析这个。它告诉我类型和消息是NOT_FOUND并建议联系Microsoft。虽然这是一条路线 - 我想知道在考虑这种方法之前是否还有其他事情可以做:

I therefore tried installing DebugDiag and looking for any exceptions, which create a number of full dumps for me. Once I've analyzed them I've got a report out the other end shown below, but I'm not sure how to further analyse this. It tells me the type and message were NOT_FOUND and suggests contacting Microsoft. While this is 1 route - I'd like to know if there are further things that can be done before considering that approach:

推荐答案

我设法找到了我的问题的原因,一个StackOverflowException,因为本地再现是可能的,并且一旦调试器被连接就很明显。

I managed to find the cause of my problem, a StackOverflowException because a local reproduction was possible and it was quite apparent once the debugger was attatched.

因此我必须假设,StackOverflowExceptions类似于OutOfMemoryExceptions,因为它使IIS不稳定,因此完全无法完成运行(甚至提供/记录异常信息)。

I've therefore got to assume, that StackOverflowExceptions are similar to OutOfMemoryExceptions in that it makes IIS unstable and therefore completely unable to complete running (even to the point of providing/logging exception information).

这篇关于如何解释此崩溃转储的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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