Databases
StackOverflow2013
Postsdbo
POiOS App: Several crashes with common themes of: SIGSEGV and _sigtramp
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POiOS App: Several crashes with common themes of: SIGSEGV and _sigtramp
    primarykey
    data
    text
    <p>Being new to obj-c I'm no master at reading stacktraces but I can usually figure out where in the code to start looking. However, during testing one of the testers is consistently reporting several random crashes. And I cannot make head nor tail of the stacktraces since they don't point to any of my own code. Here are two:</p> <pre><code>0 WIT Free 0x000a5a92 _mh_execute_header + 338578 1 WIT Free 0x000a677c _mh_execute_header + 341884 2 libsystem_c.dylib 0x355cc7ec _sigtramp + 48 3 WIT Free 0x000fcd02 _mh_execute_header + 695554 4 WIT Free 0x000fd502 _mh_execute_header + 697602 5 WIT Free 0x000fd0a0 _mh_execute_header + 696480 6 WIT Free 0x000fea9c _mh_execute_header + 703132 7 WIT Free 0x000ffa3a _mh_execute_header + 707130 8 Foundation 0x31e1bc28 __65-[NSURLConnectionInternal _withConnectionAndDelegate:onlyActive:]_block_invoke_0 + 16 9 Foundation 0x31d736d8 -[NSURLConnectionInternalConnection invokeForDelegate:] + 28 10 Foundation 0x31d736a2 -[NSURLConnectionInternal _withConnectionAndDelegate:onlyActive:] + 198 11 Foundation 0x31d735c4 -[NSURLConnectionInternal _withActiveConnectionAndDelegate:] + 60 12 CFNetwork 0x34c6c7f4 _ZN19URLConnectionClient23_clientDidFinishLoadingEPNS_26ClientConnectionEventQueueE + 192 13 CFNetwork 0x34c614a4 _ZN19URLConnectionClient26ClientConnectionEventQueue33processAllEventsAndConsumePayloadEP20XConnectionEventInfoI12XClientEvent18XClientEventParamsEl + 424 14 CFNetwork 0x34c61598 _ZN19URLConnectionClient26ClientConnectionEventQueue33processAllEventsAndConsumePayloadEP20XConnectionEventInfoI12XClientEvent18XClientEventParamsEl + 668 15 CFNetwork 0x34c611a2 _ZN19URLConnectionClient13processEventsEv + 106 16 CFNetwork 0x34c610d8 _ZN17MultiplexerSource7performEv + 156 17 CoreFoundation 0x314b1ad2 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 14 18 CoreFoundation 0x314b129e __CFRunLoopDoSources0 + 214 19 CoreFoundation 0x314b0044 __CFRunLoopRun + 652 20 CoreFoundation 0x314334a4 CFRunLoopRunSpecific + 300 21 CoreFoundation 0x3143336c CFRunLoopRunInMode + 104 22 GraphicsServices 0x334ad438 GSEventRunModal + 136 23 UIKit 0x30b96cd4 UIApplicationMain + 1080 24 WIT Free 0x000558b0 _mh_execute_header + 10416 25 WIT Free 0x00055857 _mh_execute_header + 10327 </code></pre> <p>And: </p> <pre><code>0 WIT Free 0x00067a92 _mh_execute_header + 338578 1 WIT Free 0x0006877c _mh_execute_header + 341884 2 libsystem_c.dylib 0x355cc7ec _sigtramp + 48 3 WIT Free 0x000bfc82 _mh_execute_header + 699522 4 WIT Free 0x000cc34e _mh_execute_header + 750414 5 WIT Free 0x000cd5a0 _mh_execute_header + 755104 6 libdispatch.dylib 0x35cf5c58 _dispatch_call_block_and_release + 12 7 libdispatch.dylib 0x35d00e90 _dispatch_main_queue_callback_4CF$VARIANT$up + 196 8 CoreFoundation 0x314b02ac __CFRunLoopRun + 1268 9 CoreFoundation 0x314334a4 CFRunLoopRunSpecific + 300 10 CoreFoundation 0x3143336c CFRunLoopRunInMode + 104 11 GraphicsServices 0x334ad438 GSEventRunModal + 136 12 UIKit 0x30b96cd4 UIApplicationMain + 1080 13 WIT Free 0x000178b0 _mh_execute_header + 10416 14 WIT Free 0x00017857 _mh_execute_header + 10327 </code></pre> <p>Can someone decipher this and explain what I am seeing in plain English? Some pointer to why these crashes might be occuring would also be very helpful!</p> <p><strong>Edit: More Information</strong></p> <ul> <li>Apparently the crashes almost always happen on a fairly weak network connection.</li> <li>I'm using asynchronous NSURLConnections with a delegate</li> <li>I'm going to try and get stack traces for all threads using PLCrashReporter</li> <li>I'm using ARC</li> <li>The top three lines of the trace are common to every single crash (except the hexadecimal number - memory location?):</li> </ul> <p>:</p> <pre><code>0 WIT Free 0x000a5a92 _mh_execute_header + 338578 1 WIT Free 0x000a677c _mh_execute_header + 341884 2 libsystem_c.dylib 0x355cc7ec _sigtramp + 48 </code></pre> <p>Thanks</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USdjskinner
    1. USdjskinner
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POiOS App: Several crashes with common themes of: SIGSEGV and _sigtramp
      1. This table or related slice is empty.
      1. VTUpMod
    1. COIf they don't point to your code, what is "WIT Free"? (The stack traces look odd, as if something was trying to turn addresses into symbols and doing about half the job.)
      singulars
      1. POiOS App: Several crashes with common themes of: SIGSEGV and _sigtramp
      1. USPhillip Mills
    2. COPossibly there is a mismatch between the crash info and the binary/symbols used to interpret it.
      singulars
      1. POiOS App: Several crashes with common themes of: SIGSEGV and _sigtramp
      1. USPhillip Mills
    3. COWIT Free is my code. What's this _me_execute_header all about? I cannot find anything about it on the net?
      singulars
      1. POiOS App: Several crashes with common themes of: SIGSEGV and _sigtramp
      1. USdjskinner
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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