Databases
StackOverflow2013
Postsdbo
POSymbolicateCrash is not creating proper de-symbol file
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSymbolicateCrash is not creating proper de-symbol file
    primarykey
    data
    text
    <p>I have the dSYM file for build created on client's machine. Client got a crash in build and now I am trying to de-symbol by use of the symbolicatecrash by the simple following command in terminal:</p> <pre><code>symbolicatecrash myapp_iPod-Touch.crash myapp.app.dSYM &gt; test.txt </code></pre> <p>but it's not creating any meaningful de-symboled file. and it's giving the follwoing error in terminal:</p> <pre><code>Can't understand the output from otool </code></pre> <p>then I found a solution in following link: <a href="https://stackoverflow.com/questions/1207223/iphone-sdk-3-0-and-symbolicatecrash-not-getting-along">iPhone SDK 3.0 and symbolicatecrash not getting along?</a> but still it's not de-symbolicating the exact memory location to exact code line responsible for crash.</p> <p>Then I tried some other options too: Following is the other option but didn't work:</p> <pre><code>symbolicatecrash.sh -A -v [crashlog-filename] MyApp.dSYM </code></pre> <p>For reference: <a href="http://apptech.next-munich.com/2010/01/symbolicatecrash.html" rel="nofollow noreferrer">http://apptech.next-munich.com/2010/01/symbolicatecrash.html</a></p> <p>The best option that helped me is atos command to get the exact code line number of the crash but I want the systematic symbolicatecrash to create the dump.</p> <p>NOTE: When I create build in my machine and desymbolicate (the my machine created) build's crash log in my machine it creates perfectly good dump file (show's exact memory location VS code line responsible for crash).</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USUPT
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POSymbolicateCrash is not creating proper de-symbol file
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POSymbolicateCrash is not creating proper de-symbol file
      1. USRahul Choudhary
      1. VTFavorite
    1. This table or related slice is empty.
 

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