诊断Windows事件查看器中的CLR错误 [英] Diagnosing CLR errors in Windows Event Viewer

问题描述

我们有一个在生产中崩溃的.NET桌面应用程序。我们如何诊断错误？我想知道发生的异常类型，错误消息和堆栈跟踪。

由于异常未被我们的代码处理，我们收到此应用程序遇到问题，需要关闭 Windows消息框。唯一的选择是关闭，没有调试按钮。

此MSDN文章建议在Windows事件注册表中查找。我检查了那里，这里是其中的信息：

故障应用程序Initect.Server.UI.exe，
版本0.12。 9084.90，
时间戳0x49cac472，
故障模块KERNEL32.dll，
版本6.0.6001.18000，
时间戳0x4791a81d，
异常代码0xe0434f4d，
故障偏移0x0002f35f，
进程ID 0x44c，
应用程序启动时间0x01c9ada7f320cab0

这个信息如何告诉我异常类型，堆栈跟踪和错误消息？

解决方案

该信息不足以让您获得堆栈跟踪，异常类型，错误消息等。

您可以在Windows Server 2008上配置Windows错误报告（显示您需要关闭UI的问题）来始终收集转储文件，然后你可以调试。这不需要您在生产环境中安装Visual Studio或任何其他调试器。

http://blogs.technet.com/askperf/archive/2008/02/05/ws2008-windows- error-reporting.aspx 显示正确的注册表设置。

We have an .NET desktop application that crashed in production. How do we diagnose the error? I'd like to know the type of exception that occurred, the error message, and the stack trace.

Because the exception wasn't handled by our code, we received the "This application has encountered a problem and needs to close" Windows message box. The only option was to close, there was no debug button.

This MSDN article suggested looking in the Windows Event registry. I checked there, and here's the information inside it:

Faulting application Initect.Server.UI.exe, version 0.12.9084.90, time stamp 0x49cac472, faulting module KERNEL32.dll, version 6.0.6001.18000, time stamp 0x4791a81d, exception code 0xe0434f4d, fault offset 0x0002f35f, process id 0x44c, application start time 0x01c9ada7f320cab0

How can this information tell me the exception type, the stack trace, and the error message?

解决方案

That information isn't enough to get you a stack trace, exception type, error message, etc.

You can configure Windows Error Reporting (which showed you the problem & needs to close UI) on Windows Server 2008 to always collect a dump file that you can then debug. This doesn't require you to install Visual Studio or any other debugger in your production environment.

http://blogs.technet.com/askperf/archive/2008/02/05/ws2008-windows-error-reporting.aspx shows the proper registry settings to do this.

这篇关于诊断Windows事件查看器中的CLR错误的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！