blocks|key|2054977|text|不，这将导致异常具有不同的堆栈跟踪。只有在catch处理程序中使用没有任何异常对象的throw时，堆栈跟踪才会保持不变。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2054978|无论是否重新抛出异常，您都可能希望从HandleException返回一个布尔值。|2054979|entityMap^0|L|5|16|5|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|P|8|@]|D|@]|E|$]]]|I|$]]

No, this will cause the exception to have a different stack trace. Only using a <code>throw</code> without any exception object in the <code>catch</code> handler will leave the stack trace unchanged.

You may want to return a boolean from HandleException whether the exception shall be rethrown or not.

blocks|key|1840900|text|当你执行throw+ex时，抛出的异常就变成了“原始”异常。所以所有以前的堆栈跟踪都不会出现在那里。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1840901|如果你使用throw，异常就会一直持续下去，你会得到完整的堆栈跟踪。|1840902|entityMap^0|4|8|0|5|5|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|P|8|@]|D|@]|E|$]]]|I|$]]

When you do <code>throw ex</code>, that thrown exception becomes the "original" one. So all previous stack trace will not be there.

If you do <code>throw</code>, the exception just goes down the line and you'll get the full stack trace.

blocks|key|2055230|text|从不同的角度来看，如果您正在向客户端提供API，并且希望为您的内部库提供详细的堆栈跟踪信息，那么使用throw特别有用。通过在这里使用throw，我可以获得堆栈跟踪，在本例中是File.Delete的System.IO.File库。如果我使用了抛出ex，那么这些信息将不会被传递给我的处理程序。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2055231|static+void+Main(string[]+args)+{++++++++++++
+++Method1();++++++++++++
}

static+void+Method1()+{
++++try+{
++++++++Method2();
++++}+catch+(Exception+ex)+{
++++++++Console.WriteLine("Exception+in+Method1");+++++++++++++
++++}
}

static+void+Method2()+{
++++try+{
++++++++Method3();
++++}+catch+(Exception+ex)+{
++++++++Console.WriteLine("Exception+in+Method2");
++++++++Console.WriteLine(ex.TargetSite);
++++++++Console.WriteLine(ex.StackTrace);
++++++++Console.WriteLine(ex.GetType().ToString());
++++}
}

static+void+Method3()+{
++++Method4();
}

static+void+Method4()+{
++++try+{
++++++++System.IO.File.Delete("");
++++}+catch+(Exception+ex)+{
++++++++//+Displays+entire+stack+trace+into+the+.NET+
++++++++//+or+custom+library+to+Method2()+where+exception+handled
++++++++//+If+you+want+to+be+able+to+get+the+most+verbose+stack+trace
++++++++//+into+the+internals+of+the+library+you're+calling
++++++++throw;++++++++++++++++
++++++++//+throw+ex;
++++++++//+Display+the+stack+trace+from+Method4()+to+Method2()+where+exception+handled
++++}
}|code-block|syntax|javascript|2055232|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

To give you a different perspective on this, using throw is particularly useful if you're providing an API to a client and you want to provide verbose stack trace information for your internal library. By using throw here, I'd get the stack trace in this case of the System.IO.File library for File.Delete. If I use throw ex, then that information will not be passed to my handler. 

<pre><code>static void Main(string[] args) { 
 Method1(); 
}

static void Method1() {
 try {
 Method2();
 } catch (Exception ex) {
 Console.WriteLine("Exception in Method1"); 
 }
}

static void Method2() {
 try {
 Method3();
 } catch (Exception ex) {
 Console.WriteLine("Exception in Method2");
 Console.WriteLine(ex.TargetSite);
 Console.WriteLine(ex.StackTrace);
 Console.WriteLine(ex.GetType().ToString());
 }
}

static void Method3() {
 Method4();
}

static void Method4() {
 try {
 System.IO.File.Delete("");
 } catch (Exception ex) {
 // Displays entire stack trace into the .NET 
 // or custom library to Method2() where exception handled
 // If you want to be able to get the most verbose stack trace
 // into the internals of the library you're calling
 throw; 
 // throw ex;
 // Display the stack trace from Method4() to Method2() where exception handled
 }
}
</code></pre>

blocks|key|1841277|text|让我们来理解一下抛出和抛出前两者之间的区别。我听说在许多.net采访中，这个常见的问题都被问到了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1841278|为了给出这两个术语的概述，抛出和抛出ex都用来理解异常发生的位置。Throw+ex重写异常的堆栈跟踪，而不考虑实际抛出的位置。|1841279|让我们通过一个例子来理解。|1841280|让我们先来了解一下第一次投掷。|1841281|static+void+Main(string[]+args)+{
++++try+{
++++++++M1();
++++}+catch+(Exception+ex)+{
++++++++Console.WriteLine("+-----------------Stack+Trace+Hierarchy+-----------------");
++++++++Console.WriteLine(ex.StackTrace.ToString());
++++++++Console.WriteLine("+----------------+Method+Name+/+Target+Site+--------------+");
++++++++Console.WriteLine(ex.TargetSite.ToString());
++++}
++++Console.ReadKey();
}

static+void+M1()+{
++++try+{
++++++++M2();
++++}+catch+(Exception+ex)+{
++++++++throw;
++++};
}

static+void+M2()+{
++++throw+new+DivideByZeroException();
}|code-block|syntax|javascript|1841282|上面的输出如下所示。|1841283|显示异常实际抛出的完整层次结构和方法名称。这是M2+->+M2。以及行号|1841284|​|1841285|📷|atomic|offset|length|1841286|1841287|其次..。让我们通过抛出ex来理解。只需在M2方法catch块中将throw替换为throw+ex即可。如下所示。|1841288|1841289|1841290|1841291|抛出ex代码的输出如下所示。|1841292|1841293|1841294|1841295|您可以在输出中看到区别。抛出ex只是忽略所有先前的层次结构，并用写入抛出ex的行/方法重置堆栈跟踪。|1841296|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/b072b5234a7efab75458865a0b7016f1.png|imageAlt|1|https://ask.qcloudimg.com/http-save/yehe-900000/9194f43c987e314f67ba745ab444a8c2.png|2|https://ask.qcloudimg.com/http-save/yehe-900000/34988d2859835ebb479ec3b42d9bc2c7.png^0|0|0|0|0|0|0|0|0|0|1|0|0|0|0|0|0|1|1|0|0|0|0|0|1|2|0|0|0^^$0|@$1|2|3|4|5|6|7|1N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|1P|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|1R|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|1S|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|1T|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1U|8|@]|9|@]|A|$]]|$1|S|3|T|5|U|7|1V|8|@]|9|@$V|1W|W|1X|1|1Y]]|A|$]]|$1|X|3|R|5|6|7|1Z|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|20|8|@]|9|@]|A|$]]|$1|10|3|R|5|6|7|21|8|@]|9|@]|A|$]]|$1|11|3|T|5|U|7|22|8|@]|9|@$V|23|W|24|1|25]]|A|$]]|$1|12|3|R|5|6|7|26|8|@]|9|@]|A|$]]|$1|13|3|14|5|6|7|27|8|@]|9|@]|A|$]]|$1|15|3|R|5|6|7|28|8|@]|9|@]|A|$]]|$1|16|3|T|5|U|7|29|8|@]|9|@$V|2A|W|2B|1|2C]]|A|$]]|$1|17|3|R|5|6|7|2D|8|@]|9|@]|A|$]]|$1|18|3|19|5|6|7|2E|8|@]|9|@]|A|$]]|$1|1A|3|-4|5|6|7|2F|8|@]|9|@]|A|$]]]|1B|$1C|$5|1D|1E|1F|A|$1G|1H|1I|-4]]|1J|$5|1D|1E|1F|A|$1G|1K|1I|-4]]|1L|$5|1D|1E|1F|A|$1G|1M|1I|-4]]]]

let's understand the difference between throw and throw ex. I heard that in many .net interviews this common asked is being asked.

Just to give an overview of these two terms, throw and throw ex are both used to understand where the exception has occurred. Throw ex rewrites the stack trace of exception irrespective where actually has been thrown. 

Let's understand with an example.

Let's understand first Throw.

<pre><code>static void Main(string[] args) {
 try {
 M1();
 } catch (Exception ex) {
 Console.WriteLine(" -----------------Stack Trace Hierarchy -----------------");
 Console.WriteLine(ex.StackTrace.ToString());
 Console.WriteLine(" ---------------- Method Name / Target Site -------------- ");
 Console.WriteLine(ex.TargetSite.ToString());
 }
 Console.ReadKey();
}

static void M1() {
 try {
 M2();
 } catch (Exception ex) {
 throw;
 };
}

static void M2() {
 throw new DivideByZeroException();
}
</code></pre>

output of the above is below.

shows complete hierarchy and method name where actually the exception has thrown.. it is M2 -> M2. along with line numbers

<img src="https://i.stack.imgur.com/wUu6g.png" alt="enter image description here">

Secondly.. lets understand by throw ex. Just replace throw with throw ex in M2 method catch block. as below.

<img src="https://i.stack.imgur.com/GlLqc.png" alt="enter image description here">

output of throw ex code is as below..

<img src="https://i.stack.imgur.com/V575m.png" alt="enter image description here">

You can see the difference in the output.. throw ex just ignores all the previous hierarchy and resets stack trace with line/method where throw ex is written.

blocks|key|1841324|text|最好使用throw而不是throw+ex。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1841325|抛出ex重置原始堆栈跟踪，并且找不到以前的堆栈跟踪。|1841326|如果我们使用抛出，我们将得到一个完整的堆栈跟踪。|1841327|entityMap^0|4|5|C|8|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]|$9|O|A|P|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Q|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|R|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|S|8|@]|D|@]|E|$]]]|K|$]]

It's better to use <code>throw</code> instead of <code>throw ex</code>.
throw ex reset the original stack trace and can't be found the previous stack trace.
If we use throw, we will get a full stack trace.

blocks|key|1841348|text|为了扩展Lucero的答案，这里介绍了如何在不丢失原始堆栈跟踪的情况下实现原始代码的意图。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1841349|public+class+Program+{
++++public+static+void+Main(string[]+args)+{
++++++++try+{
++++++++++++//+something
++++++++}+catch+(Exception+ex)+{
++++++++++++if+(!HandleException(ex))+throw;
++++++++}
++++}

++++///+<returns>
++++///+++true+if+the+exception+has+been+handled;
++++///+++false+if+exception+should+be+passed+along
++++///+</returns>
++++private+static+bool+HandleException(Exception+ex)+{
++++++++if+(ex+is+ThreadAbortException)+{
++++++++++++//+ignore+then,
++++++++++++return+true;
++++++++}
++++++++if+(ex+is+ArgumentOutOfRangeException)+{+
++++++++++++//+Log+then,
++++++++++++return+false;
++++++++}
++++++++if+(ex+is+InvalidOperationException)+{
++++++++++++//+Show+message+then,
++++++++++++return+false;
++++++++}
++++++++//+and+so+on.
++++}
}|code-block|syntax|javascript|1841350|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

To expand on Lucero's answer, here's how you can accomplish the intent of the original code without losing the original stack trace.
<pre><code>public class Program {
 public static void Main(string[] args) {
 try {
 // something
 } catch (Exception ex) {
 if (!HandleException(ex)) throw;
 }
 }

 /// &lt;returns&gt;
 /// true if the exception has been handled;
 /// false if exception should be passed along
 /// &lt;/returns&gt;
 private static bool HandleException(Exception ex) {
 if (ex is ThreadAbortException) {
 // ignore then,
 return true;
 }
 if (ex is ArgumentOutOfRangeException) { 
 // Log then,
 return false;
 }
 if (ex is InvalidOperationException) {
 // Show message then,
 return false;
 }
 // and so on.
 }
}
</code></pre>

There are some posts that asks what the difference between those two are already. (why do I have to even mention this...)

But my question is different in a way that I am calling "throw ex" in another error god-like handling method.

<pre><code>public class Program {
 public static void Main(string[] args) {
 try {
 // something
 } catch (Exception ex) {
 HandleException(ex);
 }
 }

 private static void HandleException(Exception ex) {
 if (ex is ThreadAbortException) {
 // ignore then,
 return;
 }
 if (ex is ArgumentOutOfRangeException) { 
 // Log then,
 throw ex;
 }
 if (ex is InvalidOperationException) {
 // Show message then,
 throw ex;
 }
 // and so on.
 }
}
</code></pre>

If <code>try &amp; catch</code> were used in the <code>Main</code>, then I would use <code>throw;</code> to rethrow the error.
But in the above simplied code, all exceptions go through <code>HandleException</code>

Does <code>throw ex;</code> has the same effect as calling <code>throw</code> when called inside <code>HandleException</code>?

Is there a difference between "throw" and "throw ex"?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

有一些帖子问这两者之间的区别是什么。(为什么我要提这件事……)但我的问题不同之处在于，我在另一种类似神的错误处理方法中调用“抛出ex”。public class Program {    public static void Main(string[] args) {        try {            /...

问“投掷”和“投掷前”有区别吗？
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问“投掷”和“投掷前”有区别吗？EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问“投掷”和“投掷前”有区别吗？
EN