HNGlance

Top Best New Show

The Top 5 Crashes on iOS

https://www.apteligent.com/developer-resources/top-5-most-frequent-crashes-on-ios/?partner_code=GDC_hn_top5ios

by andrewmlevy • 10 years ago

20 1 10 years ago

AP

Related Stories

Loading related stories...

Comments

1

makecheck• 10 years ago

The first example’s remedy seems to be wrong.

I am not aware of any reason to test for "nil" in Objective-C, as that remedy suggests. Sending the "doSomething" message to "nil" should do nothing.

If SIGSEGV does occur for an object, it is probably for the exact opposite reason: you have a pointer that is NOT "nil" but it refers to something that has been freed. (Or, the SIGSEGV is not related to objects at all, and is caused by some other access such as plain C code.)

Source preview

apteligent.com

HNGlance

© 2024-2026 HN Glance. Story content belongs to its original sources.

Privacy
Terms