Note that there are some explanatory texts on larger screens.

plurals
  1. POios app strange crash on start
    primarykey
    data
    text
    <p>My project, called OBI, works fine when launched from Xcode, but when I create <code>.ipa</code> file its crashes with provided log. In project no classes with names: <code>Mutex</code>, <code>DelayedPointerDeletionManager</code> or <code>MemoryManager</code>, so I can't understood from where this exception.</p> <pre><code>Thread 0 Crashed: 0 libsystem_pthread.dylib 0x396b7046 _pthread_mutex_check_init + 14 1 libsystem_pthread.dylib 0x396b6e32 _pthread_mutex_lock + 22 2 OBI 0x02a74f20 Mutex::Lock() (Mutex.cpp:152) 3 OBI 0x02838930 DelayedPointerDeletionManager::AddPointerToMainThreadDealloc(void*, MemLabelId) (Mutex.h:32) 4 OBI 0x028384a4 MemoryManager::Deallocate(void*, MemLabelId) (MemoryManager.cpp:1082) 5 OBI 0x028384e4 operator delete[](void*) (MemoryManager.cpp:114) 6 OBI 0x01d28010 std::locale::locale&lt;boost::filesystem::detail::utf8_codecvt_facet&gt;(std::locale const&amp;, boost::filesystem::detail::utf8_codecvt_facet*) (locale_classes.h:581) 7 OBI 0x01d281c4 ___lldb_unnamed_function148423$$OBI + 232 8 dyld 0x2be5b59e ImageLoaderMachO::doModInitFunctions(ImageLoader::LinkContext const&amp;) + 174 9 dyld 0x2be5b6ac ImageLoaderMachO::doInitialization(ImageLoader::LinkContext const&amp;) + 16 10 dyld 0x2be58d34 ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&amp;, unsigned int, ImageLoader::InitializerTimingList&amp;) + 356 11 dyld 0x2be58b88 ImageLoader::runInitializers(ImageLoader::LinkContext const&amp;, ImageLoader::InitializerTimingList&amp;) + 36 12 dyld 0x2be4fd38 dyld::initializeMainExecutable() + 164 13 dyld 0x2be52ab4 dyld::_main(macho_header const*, unsigned long, int, char const**, char const**, char const**, unsigned long*) + 1748 14 dyld 0x2be4f22a dyldbootstrap::start(macho_header const*, int, char const**, long, macho_header const*, unsigned long*) + 346 15 dyld 0x2be4f064 _dyld_start + 60 </code></pre> <p>Edit, few lines from console. </p> <pre><code>Oct 16 14:43:18 Sergiys-iPad kernel[0] &lt;Debug&gt;: launchd[9526] Container: /private/var/mobile/Applications/AA46736B-6348-42BA-A8F0-DD63DC535AF6 (sandbox) Oct 16 14:43:19 Sergiys-iPad ReportCrash[9527] &lt;Notice&gt;: ReportCrash acting against PID 9526 Oct 16 14:43:19 Sergiys-iPad ReportCrash[9527] &lt;Notice&gt;: Formulating crash report for process OBI[9526] Oct 16 14:43:19 Sergiys-iPad com.apple.launchd[1] (UIKitApplication:com.mycompany.OBIQA[0x14dc][9526]) &lt;Warning&gt;: (UIKitApplication:com.mycompany.OBIQA[0x14dc]) Job appears to have crashed: Segmentation fault: 11 Oct 16 14:43:19 Sergiys-iPad com.apple.launchd[1] (UIKitApplication:com.mycompany.OBIQA[0x14dc]) &lt;Notice&gt;: (UIKitApplication:com.mycompany.OBIQA[0x14dc]) Throttling respawn: Will start in 2147483647 seconds Oct 16 14:43:19 Sergiys-iPad backboardd[28] &lt;Warning&gt;: Application 'UIKitApplication:com.mycompany.OBIQA[0x14dc]' exited abnormally with signal 11: Segmentation fault: 11 Oct 16 14:43:19 Sergiys-iPad SpringBoard[33] &lt;Warning&gt;: Application 'com.mycompany.OBIQA' has failed to launch too many times. Not relaunching. Oct 16 14:43:19 Sergiys-iPad ReportCrash[9527] &lt;Notice&gt;: Saved crashreport to /var/mobile/Library/Logs/CrashReporter/OBI_2013-10-16-144319_Sergiys-iPad.plist using uid: 0 gid: 0, synthetic_euid: 501 egid: 0 </code></pre> <p>I will be very pleased for any help, or direction to dig </p> <p><strong>EDIT</strong> Finally I found what causes this exception. Is <code>symbol striping</code> option in build setting, after I changed it from <code>all symbols</code> to <code>debug symbols</code> everything become fine.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload