在安全处理异常时避免首次机会异常消息

Avoiding first chance exception messages when the exception is safely handled(在安全处理异常时避免首次机会异常消息)
本文介绍了在安全处理异常时避免首次机会异常消息的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

以下代码捕获 EOS 异常

The following bit of code catches the EOS Exception

using (var reader = new BinaryReader(httpRequestBodyStream)) {

    try {
        while (true) {
            bodyByteList.Add(reader.ReadByte());
        }
    } catch (EndOfStreamException) { }
}

那么为什么我仍然会在我的控制台中收到第一次机会异常?

So why do I still receive first-chance exceptions in my console?

在 mscorlib.dll 中发生了System.IO.EndOfStreamException"类型的第一次机会异常

A first chance exception of type 'System.IO.EndOfStreamException' occurred in mscorlib.dll

有没有办法隐藏这些首次机会异常消息?

Is there a way to hide these first chance exception messages?

推荐答案

第一次机会"异常的关键在于您正在看到它们的预处理程序,以便您可以在调试期间在抛出点停止它们.第二次机会"异常是没有适当处理程序的异常.有时您想捕获第一次机会"异常,因为重要的是要查看抛出异常时发生的情况,即使有人正在捕获它.

The point of "first-chance" exceptions is that you're seeing them pre-handler so that you can stop on them during debugging at the point of throwing. A "second-chance" exception is one that has no appropriate handler. Sometimes you want to catch "first-chance" exceptions because it's important to see what's happening when it's being thrown, even if someone is catching it.

没什么好担心的.这是正常行为.

There's nothing to be concerned with. This is normal behavior.

这篇关于在安全处理异常时避免首次机会异常消息的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持编程学习网!

本站部分内容来源互联网,如果有图片或者内容侵犯您的权益请联系我们删除!

相关文档推荐

DispatcherQueue null when trying to update Ui property in ViewModel(尝试更新ViewModel中的Ui属性时DispatcherQueue为空)
Drawing over all windows on multiple monitors(在多个监视器上绘制所有窗口)
Programmatically show the desktop(以编程方式显示桌面)
c# Generic Setlt;Tgt; implementation to access objects by type(按类型访问对象的C#泛型集实现)
InvalidOperationException When using Context Injection in ASP.Net Core(在ASP.NET核心中使用上下文注入时发生InvalidOperationException)
LINQ many-to-many relationship, how to write a correct WHERE clause?(LINQ多对多关系,如何写一个正确的WHERE子句?)