blocks|key|2734791|text|下面将提供一个未处理的异常，并要求您选择调试器：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2734792|System.Diagnostics.Debugger.Launch()|code-block|syntax|javascript|2734793|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|$]]

The following will provide an unhandled exception and will ask for you to choose a debugger:

<pre><code>System.Diagnostics.Debugger.Launch()
</code></pre>

blocks|key|1412922|text|抛出异常:)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1412923|throw+new+Exception("Your+exception+here!");|code-block|syntax|javascript|1412924|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|$]]

Throw an exception :)

<pre><code>throw new Exception("Your exception here!");
</code></pre>

blocks|key|2734821|text|+int[]+x+=+{0};
+int+blah+=+x[2];|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|2734822|也会导致异常|unstyled|2734823|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|J|8|@]|9|@]|A|$]]|$1|G|3|-4|5|F|7|K|8|@]|9|@]|A|$]]]|H|$]]

<pre><code> int[] x = {0};
 int blah = x[2];
</code></pre>

will cause an exception just as well

blocks|key|2734853|text|做这件事的一个肯定的方法是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2734854|ThreadPool.QueueUserWorkItem(new+WaitCallback(ignored+=>+
{
+++throw+new+Exception();
}));|code-block|syntax|javascript|2734855|所有其他的都可以由顶级的ApplicationDomain.OnUnhandledException等来处理。|2734856|这个程序会杀死它(假设是.NET+2.0%2B，而不是使用'legacyUnhandledExceptionPolicy'：http://msdn.microsoft.com/en-us/library/ms228965.aspx)。|offset|length|2734857|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/ms228965.aspx^0|0|0|0|1O|1H|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|W|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|X|8|@]|9|@$K|Y|L|Z|1|10]]|A|$]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T]]]]

A surefire way to do it is as follows:

<pre><code>ThreadPool.QueueUserWorkItem(new WaitCallback(ignored =&gt; 
{
 throw new Exception();
}));
</code></pre>

All the others can be handled by the top level ApplicationDomain.OnUnhandledException and the like.

This one will kill it dead (assuming .NET 2.0+, and not using 'legacyUnhandledExceptionPolicy': <a href="http://msdn.microsoft.com/en-us/library/ms228965.aspx" rel="noreferrer">http://msdn.microsoft.com/en-us/library/ms228965.aspx</a>).

blocks|key|1413001|text|使用下面的代码关闭应用程序。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1413002|Environment.Exit(1);++++|code-block|syntax|javascript|1413003|Exit需要一个名为exitcode的参数。如果exitcode=0意味着没有错误。提供一个非零退出代码以反映错误.|1413004|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Use below code to close the application.

<pre><code>Environment.Exit(1); 
</code></pre>

Exit needs a parameter called exitcode. If exitcode=0 means there was no error. Supply a non-zero exit code to to reflect an error.

blocks|key|2734963|text|StackOverflowException是个坏蛋：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2734964|void+PerformOverflow()
{
++PerformOverflow();
}|code-block|syntax|javascript|2734965|用法：|2734966|PerformOverflow();|2734967|entityMap^0|0|M|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|T|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|U|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|V|8|@]|D|@]|E|$I|J]]|$1|O|3|-4|5|6|7|W|8|@]|D|@]|E|$]]]|P|$]]

<code>StackOverflowException</code> is a badass:

<pre><code>void PerformOverflow()
{
 PerformOverflow();
}
</code></pre>

Usage:

<pre><code>PerformOverflow();
</code></pre>

blocks|key|337032|text|没有一个答案像我所寻找的那样破坏了我的应用程序。这就是对我有用的方法。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|337033|++++private+void+Form1_Load(object+sender,+EventArgs+e)
++++{
++++++++object+p+=+0;
++++++++IntPtr+pnt+=+(IntPtr)0x123456789;
++++++++Marshal.StructureToPtr(p,+pnt,+false);
++++}|code-block|syntax|javascript|337034|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|$]]

None of the answers crashed my app the way I was looking for. So here is the approach that worked for me.

<pre><code> private void Form1_Load(object sender, EventArgs e)
 {
 object p = 0;
 IntPtr pnt = (IntPtr)0x123456789;
 Marshal.StructureToPtr(p, pnt, false);
 }
</code></pre>

blocks|key|337038|text|++public+void+Loop()
++{
++++++Loop();
++}
++//call+this
++Loop();|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|337039|unstyled|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$B|C]]|$1|D|3|-4|5|E|7|H|8|@]|9|@]|A|$]]]|F|$]]

<pre><code> public void Loop()
 {
 Loop();
 }
 //call this
 Loop();
</code></pre>

blocks|key|1413053|text|井。真正有效的100%25崩溃CLR的唯一方法是将本机异常注入托管世界。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1413054|直接调用Kernel32.dll的RaiseException()将立即使任何C#应用程序崩溃，同时还会导致Unity崩溃。|1413055|[DllImport("kernel32.dll")]
static+extern+void+RaiseException(uint+dwExceptionCode,+uint+dwExceptionFlags,++uint+nNumberOfArguments,+IntPtr+lpArguments);

void+start()
{
++++RaiseException(13,+0,+0,+new+IntPtr(1));
}|code-block|syntax|javascript|1413056|愉快的崩溃。请注意，为了调试本机和托管的，需要运行两个Visual实例。如果您正在开发本机P/INVOKE插件，请将Visual实例1设置为本机调试器，并将统一程序或C#程序用作宿主程序，并从另一个Visual实例附加到主机程序。|1413057|entityMap^0|N|2|0|0|0|G|4|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|T|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|U|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|V|8|@$9|W|A|X|B|C]]|D|@]|E|$]]|$1|O|3|-4|5|6|7|Y|8|@]|D|@]|E|$]]]|P|$]]

Well. The only good 100% way actualy crash CLR is to inject a native exception into the managed world. 

Calling the Kernel32.dll's RaiseException() directly will immediately crash ANY C# application, and Unity Editor as well.

<pre><code>[DllImport("kernel32.dll")]
static extern void RaiseException(uint dwExceptionCode, uint dwExceptionFlags, uint nNumberOfArguments, IntPtr lpArguments);

void start()
{
 RaiseException(13, 0, 0, new IntPtr(1));
}
</code></pre>

Happy crashing. Please note that in order to debug native and managed, you will need two instances of Visual Studio running. If you are developing native P/INVOKE plugin, set up it that Visual Studio Instance 1 is native debugger and uses Unity or your C# program as a Host program, and you attach to the Host program from another Visual Studio Instance.

blocks|key|337100|text|如果您试图转换一个空游戏对象，就可以很容易地进行复制。例如，如下所示：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|337101|public+static+GameObject+gameObjectCrash;
public+void+GenerateCrash()
{
++++gameObjectCrash.transform.rotation+=+Quaternion.Euler(90,+0,+0);
}|code-block|syntax|javascript|337102|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|$]]

It's easy enough to reproduce if you try to transform a null game object. For example, like this:

<pre><code>public static GameObject gameObjectCrash;
public void GenerateCrash()
{
 gameObjectCrash.transform.rotation = Quaternion.Euler(90, 0, 0);
}
</code></pre>

blocks|key|2735162|text|C#+in+Unity3D|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2735163|有UnityEngine.Diagnostics.Utils.ForceCrash+(在统一2018.3中)|2735164|这可以与以下ForcedCrashCategory枚举参数之一一起使用：|CODE|2735165|AccessViolation
通过在每个平台上执行无效内存access.The无效内存访问导致崩溃，如下所示：
FatalError
使用联合的本机致命错误实现造成崩溃。
Abort
通过调用abort()函数导致崩溃。
PureVirtualFunction
通过调用纯虚拟函数来引发异常，从而导致崩溃。|blockquote|2735166|对于的旧版本，统一的：|2735167|UnityEngine.Application.ForceCrash(int+mode)|2735168|对于更旧的版本(统一5)：|2735169|UnityEngine.Application.CommitSuicide(int+mode)|2735170|根据我的经验，模式0会导致“统一处理”崩溃(出现了统一崩溃对话框)，模式2则会导致出现Windows错误对话框的“硬”崩溃。|2735171|这似乎与Smilediver的这篇文章+on+mode相一致。|2735172|0-将模拟崩溃，1-将模拟联合捕获的致命错误，2-将调用abort()。|2735173|(这些方法没有记录在案，因为它们本来是供团结组织内部使用的。它们也可能被标记为[Obsolete]，这取决于您的统一版本。)|2735174|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.unity3d.com/2019.2/Documentation/ScriptReference/Diagnostics.Utils.ForceCrash.html|1|https://docs.unity3d.com/2019.2/Documentation/ScriptReference/Diagnostics.ForcedCrashCategory.html|2|https://forum.unity.com/threads/application-commitsuicide-int-mode.46495/#post-1697831^0|6|7|0|1|14|0|0|6|J|6|J|1|0|0|F|1L|A|2F|5|34|J|0|2|8|0|0|18|0|0|0|1B|0|0|N|4|4|F|2|0|0|13|A|0^^$0|@$1|2|3|4|5|6|7|1F|8|@$9|1G|A|1H|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1I|8|@]|D|@$9|1J|A|1K|1|1L]]|E|$]]|$1|H|3|I|5|6|7|1M|8|@$9|1N|A|1O|B|J]]|D|@$9|1P|A|1Q|1|1R]]|E|$]]|$1|K|3|L|5|M|7|1S|8|@$9|1T|A|1U|B|C]|$9|1V|A|1W|B|C]|$9|1X|A|1Y|B|C]|$9|1Z|A|20|B|C]]|D|@]|E|$]]|$1|N|3|O|5|6|7|21|8|@$9|22|A|23|B|C]]|D|@]|E|$]]|$1|P|3|Q|5|6|7|24|8|@$9|25|A|26|B|J]]|D|@]|E|$]]|$1|R|3|S|5|6|7|27|8|@]|D|@]|E|$]]|$1|T|3|U|5|6|7|28|8|@$9|29|A|2A|B|J]]|D|@]|E|$]]|$1|V|3|W|5|6|7|2B|8|@]|D|@]|E|$]]|$1|X|3|Y|5|6|7|2C|8|@$9|2D|A|2E|B|J]]|D|@$9|2F|A|2G|1|2H]]|E|$]]|$1|Z|3|10|5|M|7|2I|8|@]|D|@]|E|$]]|$1|11|3|12|5|6|7|2J|8|@$9|2K|A|2L|B|J]]|D|@]|E|$]]|$1|13|3|-4|5|6|7|2M|8|@]|D|@]|E|$]]]|14|$15|$5|16|17|18|E|$19|1A]]|1B|$5|16|17|18|E|$19|1C]]|1D|$5|16|17|18|E|$19|1E]]]]

For C# in Unity3D 

There is <a href="https://docs.unity3d.com/2019.2/Documentation/ScriptReference/Diagnostics.Utils.ForceCrash.html" rel="noreferrer"><code>UnityEngine.Diagnostics.Utils.ForceCrash</code></a> (in Unity 2018.3)

This can be used with one of the following <a href="https://docs.unity3d.com/2019.2/Documentation/ScriptReference/Diagnostics.ForcedCrashCategory.html" rel="noreferrer"><code>ForcedCrashCategory</code></a> enum parameter:

<blockquote>
 AccessViolation
 
 Cause a crash by performing an invalid memory
 access.The invalid memory access is performed on each platform as
 follows:
 
 FatalError
 
 Cause a crash using Unity's native fatal error
 implementation.
 
 Abort
 
 Cause a crash by calling the abort() function.
 
 PureVirtualFunction
 
 Cause a crash by calling a pure virtual function
 to raise an exception.
</blockquote>

<hr>

For older versions of Unity:

<code>UnityEngine.Application.ForceCrash(int mode)</code>

For even older versions (Unity 5):

<code>UnityEngine.Application.CommitSuicide(int mode)</code>

From my experience, mode 0 causes a "unity handled" crash (where the Unity crash dialog appears), and mode 2 causes a "hard" crash where the Windows error dialog appears.

This seems consistent with <a href="https://forum.unity.com/threads/application-commitsuicide-int-mode.46495/#post-1697831" rel="noreferrer">this post by Smilediver</a> on <code>mode</code>:

<blockquote>
 0 - will simulate crash, 1 - will simulate a fatal error that Unity
 has caught, 2 - will call abort().
</blockquote>

(These methods are not documented as they were intended for Unity's internal use. They may also be marked <code>[Obsolete]</code> depending on your Unity version.)

blocks|key|337179|text|另一个选择是|type|unstyled|depth|inlineStyleRanges|entityRanges|data|337180|System.Environment.FailFast("Error+happened")|code-block|syntax|javascript|337181|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|$]]

Another option is to call

<pre><code>System.Environment.FailFast("Error happened")
</code></pre>

blocks|key|1413182|text|我认为在早期的统一版本中有这样的代码|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1413183|Application.commitSuicide(number+Input);+|code-block|syntax|javascript|1413184|现在它被替换为|1413185|Application.ForceCrash(number+input);+|1413186|到目前为止，我不知道数字输入的不同程度，但对我来说，|1413187|Application.ForceCrash(1);+|1413188|做这份工作。|1413189|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|W|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|Y|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

I think there was a code in earlier unity versions like
<pre><code>Application.commitSuicide(number Input); 
</code></pre>
Now it is replaced by
<pre><code>Application.ForceCrash(number input); 
</code></pre>
Till this point, I dont know what different numbers do in number input, but for me,
<pre><code>Application.ForceCrash(1); 
</code></pre>
does the job.

blocks|key|337231|text|你也可以除以零，|type|unstyled|depth|inlineStyleRanges|entityRanges|data|337232|z+=+0;+
int+divide+=+1+/+x;|code-block|syntax|javascript|337233|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|$]]

you could also divide by zero,
<pre><code>z = 0; 
int divide = 1 / x;
</code></pre>

I want to test if my application crash dump can be debugged. But firstly, I need to generate a crash dump of my application. I'm using C# to code my app, and have tried with many exceptions and unsafe code etc. but don't get it. 

Thanks! 

Edit: Sorry, Just forgot something, I'm making the application with Unity3D, which handles exceptions for me automatically.

Edit 2: Thanks all for your answers. I've tested your suggestions in a standard C# application and it all works fine, but not in my Unity3D application (written with C#). It seems like Unity3D requires more effort to cause a crash, I might email Unity3D to get a answer. I will post here if I get it. Cheers!

How to make C# application crash

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我想测试我的应用程序崩溃转储是否可以调试。但是首先，我需要生成我的应用程序的崩溃转储。我正在使用C#对我的应用程序进行编码，并且尝试了很多例外和不安全的代码等等，但是没有得到它。谢谢!编辑:对不起，我忘了一些东西，我正在用Unity3D制作应用程序，它会自动为我处理异常。编辑2:感谢大家的回答。我已经在一个标准的C#应...

问如何使C#应用程序崩溃
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何使C#应用程序崩溃EN