blocks|key|3055979|text|在Objective-C中，直接使用C会导致错误访问|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3055980|strcpy(0,+"bla");|code-block|syntax|javascript|3055981|注意:虽然这可以在我所知道的任何系统上运行--在未来版本的C运行时或编译器中，这可能不会再导致崩溃。参见)|3055982|(在swift中，你必须桥接到objC才能做到这一点)|3055983|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

in Objective-C use C directly to cause a bad access

<pre><code>strcpy(0, "bla");
</code></pre>

Note: while this works on any system I know -- in a future version of the C runtime OR the compiler this might not lead to a crash anymore. see <a href="https://stackoverflow.com/questions/13651642/is-null-pointer-dereference-defined-behavior-in-objective-c">Is null pointer dereference undefined behavior in Objective-C?</a>)

(in swift you would have to bridge to objC to do this)

blocks|key|204319|text|我现在最喜欢的：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|204320|assert(!+"crashing+on+purpose+to+test+<insert+your+reason+here>");|code-block|syntax|javascript|204321|一个经典的例子：|204322|kill(+getpid(),+SIGABRT+);|204323|和一些pr0n：|204324|*(long*)0+=+0xB16B00B5;|204325|它们都会生成我的崩溃报告工具所捕获的崩溃。|204326|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|$]]

My current favourite:

<pre><code>assert(! "crashing on purpose to test &lt;insert your reason here&gt;");
</code></pre>

A classic:

<pre><code>kill( getpid(), SIGABRT );
</code></pre>

And some pr0n:

<pre><code>*(long*)0 = 0xB16B00B5;
</code></pre>

All of them generate crashes captured by my crash reporting tool.

blocks|key|2843116|text|因为我们都使用Clang+for+iOS，所以这是相当可靠的：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2843117|__builtin_trap();|code-block|syntax|javascript|2843118|这样做的好处是它就是为这个目的而设计的，所以它不应该生成任何编译器警告或错误。|2843119|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|$]]

Since we all use Clang for iOS, this is fairly reliable:

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

This has the benefit that it's designed for exactly this purpose, so it shouldn't generate any compiler warnings or errors.

blocks|key|3056260|text|一个好的旧堆栈溢出怎么样:)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3056261|-+(void)stackOverflow
{
++++[self+stackOverflow];
}|code-block|syntax|javascript|3056262|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|$]]

How about a good old stack overflow :)

<pre><code>- (void)stackOverflow
{
 [self stackOverflow];
}
</code></pre>

blocks|key|204343|text|abort();导致异常终止…这是一次撞车。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|204344|entityMap^0|0|8|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

<code>abort();</code> causes abnormal termination… That is a crash.

blocks|key|208563|text|最受欢迎的一个无法识别的选择器崩溃：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|208564|NSObject+*object+=+[[NSObject+alloc]+init];
[object+performSelector:@selector(asfd)];|code-block|syntax|javascript|208565|确保你没有在那个类中实现-asdf方法|208566|或索引超出界限异常：|208567|NSArray+*+array+=+[NSArray+array];
[array+objectAtIndex:5];|208568|当然还有kill(+getpid(),+SIGABRT+);|offset|length|style|CODE|208569|entityMap^0|0|0|0|0|0|4|Q|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|@]|A|$]]|$1|K|3|L|5|D|7|Y|8|@]|9|@]|A|$E|F]]|$1|M|3|N|5|6|7|Z|8|@$O|10|P|11|Q|R]]|9|@]|A|$]]|$1|S|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|T|$]]

Most popular one - unrecognised selector crash:

<pre><code>NSObject *object = [[NSObject alloc] init];
[object performSelector:@selector(asfd)];
</code></pre>

Make sure you don't have -asdf method implemented in that class haha

Or index beyond bound exception:

<pre><code>NSArray * array = [NSArray array];
[array objectAtIndex:5];
</code></pre>

And of course
<code>kill( getpid(), SIGABRT );</code>

blocks|key|207162|text|我认为在Swift中你很容易抛出一个致命的错误：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|207163|func+foo()+{
++++fatalError("crash!")
}|code-block|syntax|javascript|207164|实际上，它甚至打算在出现错误的情况下使用此功能，以使应用程序崩溃。|207165|为了避免在特殊情况下使用if语句，您也可以使用precondition。它类似于assert，因此它的意图(如果需要)非常明确，并且在最终版本中不会作为assert删除。它的用法与precondition(myBoolean,+"This+is+a+helpful+error+message+for+debugging.")类似。|offset|length|style|CODE|207166|entityMap^0|0|0|0|N|C|14|6|24|6|2I|21|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|T|8|@$K|U|L|V|M|N]|$K|W|L|X|M|N]|$K|Y|L|Z|M|N]|$K|10|L|11|M|N]]|9|@]|A|$]]|$1|O|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|P|$]]

I think in Swift you could easily throw a fatal error:

<pre><code>func foo() {
 fatalError("crash!")
}
</code></pre>

It is actually even intended to use this feature in case something goes wrong in order to make the app crash.

To avoid an if statement in a special case, you could use <code>precondition</code>, too. It's similar to <code>assert</code>, makes thus the intention (if wanted) pretty clear and is not removed in the final release as <code>assert</code>. It is used like <code>precondition(myBoolean, "This is a helpful error message for debugging.")</code>.

blocks|key|3055954|text|向已释放的对象发送消息|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3055955|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Send a message to a deallocated object

blocks|key|204377|text|exit(0);|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|204378|(必须...键入...30个字符)|unstyled|204379|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>exit(0);
</code></pre>

(must... type... 30 characters)

blocks|key|3055975|text|您还可以引发异常：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3055976|[NSException+raise:NSInternalInconsistencyException
++++++++++++format:@"I+want+to+test+app+crashes!."];|code-block|syntax|javascript|3055977|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 can also raise an exception:

<pre><code>[NSException raise:NSInternalInconsistencyException
 format:@"I want to test app crashes!."];
</code></pre>

blocks|key|3056153|text|将手势识别器添加到可以识别10个手指轻敲的视图中(对于iPhone+as+10，5个手指可能会有点拥挤)。GR有一个附加的方法，可以执行前面提到的任何一种可靠的方法来使你的应用程序崩溃。大多数用户不会把10根手指放在你的应用程序上，所以你是安全的，不会被普通用户意外地导致崩溃。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3056154|然而，在提交给苹果之前，你应该能够使用像Testflight这样的东西，或者只是将它部署到个人设备上，并在野外进行测试。强制崩溃可能会让你的应用程序被苹果拒绝。|3056155|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Add a gesture recognizer to a view that recognizes a 10 finger tap (5 fingers for iPhone as 10 can get a bit crowded). The GR has a method attached to it that executes anyone of the previously mentioned surefire ways to get your app to crash. Most users are not going to lay 10 fingers down on your app, so you're safe from the general user accidentally causing the crash.

However you should be able to use something like Testflight or just deploying it to personal devices and test in the wild before ever submitting it to Apple. Having a forced crash could get your app rejected by Apple.

blocks|key|206557|text|可以尝试像这样的东西|type|unstyled|depth|inlineStyleRanges|entityRanges|data|206558|NSArray*+crashingArray+=+[NSArray+arrayWithCapacity:1];
[crashingArray+release];|code-block|syntax|javascript|206559|应该在EXC_BAD_ACCESS上崩溃(可能需要第二次释放它，但正常情况下它应该已经崩溃了)|206560|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|$]]

could try something like

<pre><code>NSArray* crashingArray = [NSArray arrayWithCapacity:1];
[crashingArray release];
</code></pre>

should crash on an EXC_BAD_ACCESS (might need to release it a second time but normaly it should crash like this already)

blocks|key|204333|text|我会选择：int+raise(int+sig);|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|204334|获取更多信息>man+raise|204335|entityMap^0|5|J|0|6|A|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|$]]

I will go with:<code>int raise(int sig);</code>

To get more info <code>&gt;man raise</code>

blocks|key|204389|text|我只会正常地终止这个进程：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|204390|kill(getpid(),+SIGKILL);|code-block|syntax|javascript|204391|因此，如果你安装了一个带信号的处理程序，你也可以处理崩溃，完成写打开的文件和这些事情。|204392|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|$]]

I would just kill the process normally: 

<pre><code>kill(getpid(), SIGKILL);
</code></pre>

So if you install a handler with signal you can also handle the crash, finishing to write opened files and these things.

blocks|key|204406|text|我使用|type|unstyled|depth|inlineStyleRanges|entityRanges|data|204407|[self+doesNotRecognizeSelector:_cmd];+|code-block|syntax|javascript|204408|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|$]]

I use 

<pre><code>[self doesNotRecognizeSelector:_cmd]; 
</code></pre>

blocks|key|2843322|text|在使用RubyMotion时，我使用以下代码：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2843323|++++n=Pointer.new+('c',+1)
++++n[1000]+='h'|code-block|syntax|javascript|2843324|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|$]]

When working with RubyMotion I use this:

<pre><code> n=Pointer.new ('c', 1)
 n[1000] ='h'
</code></pre>

blocks|key|207170|text|试试这个：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|207171|-+(IBAction)Button:(id)sender
{
++++NSArray+*array+=+[NSArray+new];
++++NSLog(@"%25@",[array+objectAtIndex:8]);
}|code-block|syntax|javascript|207172|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|$]]

Try this:

<pre><code>- (IBAction)Button:(id)sender
{
 NSArray *array = [NSArray new];
 NSLog(@"%@",[array objectAtIndex:8]);
}
</code></pre>

blocks|key|2843239|text|错误的NSLog语句就可以做到这一点|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2843240|NSLog(@"%25@",1);|code-block|syntax|javascript|2843241|entityMap^0|3|5|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|P|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|L|$]]

a wrong <code>NSLog</code> statement will do it

<pre><code>NSLog(@"%@",1);
</code></pre>

I want to test my app's crash reporting out in the field by deliberately having it crash when the user performs a particular action that a real user is unlikely to do accidentally.

But what's a good reliable way of making the app crash that doesn't create a warning at compile time?

Edit: Note that many seemingly obvious answers to this question result in exceptions that get caught by Cocoa and thus don't result in the app crashing.

What's a reliable way to make an iOS app crash?

Objective-C

编译器

Swift

我想要在现场测试我的应用程序的崩溃报告，当用户执行一个真正的用户不太可能无意中做的特定操作时，故意让它崩溃。但是，有什么可靠的好方法可以让应用程序崩溃，而不会在编译时产生警告呢？编辑：请注意，这个问题的许多看似显而易见的答案都会导致异常，这些异常会被Cocoa捕获，因此不会导致应用程序崩溃。

问让iOS应用崩溃的可靠方法是什么？
EN

回答 18

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问让iOS应用崩溃的可靠方法是什么？EN

回答 18

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问让iOS应用崩溃的可靠方法是什么？
EN