Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The first thing I'd try is to map the crash stack trace to function names in your application. This may yield useful insight into the nature of the crash:</p> <ol> <li>As soon as a crash is reported request the crash log. This can be obtained through Xcode's organizer or if that's not an option it can be screen-captured from the iPhone's Settings -> General -> About -> Diagnostics &amp; Usage -> Diagnostic &amp; Usage Data. Scroll to the app name or the section LatestCrash-AppName.plist.</li> <li>Although you can in theory symbolicate a crash, I find the procedure described below a foolproof way to get symbols from the stack. Convert all stack addresses for the crashing thread into method names.</li> <li>Optionally request the iDevice syslog. This may include assertion failure messages which are also invaluable. Note that this should be done as quickly as possible as the syslog only holds so many entries before they get dropped. You can use the Organizer or the cmd line idevicesyslog to obtain this.</li> </ol> <p>Manual symbolication: This will work as long as your builds have debug information.</p> <ol> <li>Obtain the _exact_same_ .ipa that crashed. If you didn't save it you can download it from the device by using iFunBox or the cmd line ideviceinstaller utility.</li> <li>Unzip the .ipa</li> <li><p>Run the following command on the executable file (Payload/AppName.app/AppName):</p> <p>otool -tv AppName.app | c++filt > listing.asm</p></li> <li><p>Wait while the previous step completes (may take a while). The generated listing.asm file will be several megabytes long.</p></li> <li>Using an editor that can handle large files search listing.asm for the addresses listed in the stack trace. Note that the addresses may be a few bytes off (usually pointing 3 or so bytes ahead). Also, addresses that aren't found in listing.asm indicate addresses in iOS libraries. Ignore those for now.</li> </ol> <p>Of course, if you're able to symbolicate, you can skip this procedure.</p> <p>Good luck debugging!</p>
    singulars
    1. This table or related slice is empty.
    1. POOnly crashing on Testflight
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USBlanka
    1. USBlanka
    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.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COHey, Yeh we are symbolicating through Testflight already - uploading the dSYM
      singulars
      1. PO
      1. USdaidai
    2. COWhat does the symbolicated stack trace of the crashing thread say? That's golden information.
      singulars
      1. PO
      1. USBlanka
 

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