symbolicatecrash

symbolicatecrash with XCode 4.2 not symbolicating system symbols

旧街凉风 提交于 2019-12-18 11:28:34
问题 This is a very weird problem. I think I must be doing something wrong, but I don't know what it is. I've been using symbolicatecrash for several years with no problems. The issue I'm seeing is that symbolicatecrash is not showing symbols for the system libraries, but it IS showing symbols for my application. I've tried everything I can think of to resolve this with no luck. Note that I'm getting the same results on three different machines, 2 Lion, 1 Snow Leopard. Example command line:

Xcode Crash Organizer does Not Symbolicate .xccrashpoint Files

吃可爱长大的小学妹 提交于 2019-12-17 18:06:39
问题 The new Xcode 7 "Crashes" tab in the organizer shows a handful of crashes from the AppStore for my app. According to the documentation, there should be a stack trace. However, none of the 6 crashes have symbolicated stack traces: I've tried clicking "Open in Project" but it's just as useless: Of course, I included the dsym and debug info when I submitted to the store. I still have the submission build in my organizer, so the dsyms are still present on my machine. How can I get a proper stack

iOS 8 - Unable to symbolicate symbols coming from custom dynamic framework

回眸只為那壹抹淺笑 提交于 2019-12-14 02:36:29
问题 Here is what I have: - iOS app called VacationSpots (.APP file) app dSYM file dynamic framework named VSUtilities (.framework file) dynamic framework dSYM file Here is the sample project source code: https://www.dropbox.com/s/nl32xlk98lnl1mv/VacationSpots.zip?dl=0 I made the app crash at launch by force unwrapping a nil optional. Below is part of the symbolicated crash report. Notice that VSUtilities calls are not symbolicated: Thread 0 name: Dispatch queue: com.apple.main-thread Thread 0

iOS Crash Log Help Needed

一个人想着一个人 提交于 2019-12-14 02:32:22
问题 I've been receiving a few crash logs for a bug that I haven't been able to replicate. The crash occurs right when the user taps on a textView in the app. The textView is located under a tableView and I extend the bottom constraint of the textView to fit the keyboard on screen. The constraint extends through keyboard notifications (NSNotificationCenter keyboardWillShow). Below are two crash logs. Any help would be appreciated! Exception Type: EXC_CRASH (SIGABRT) Exception Codes:

How to understand this crash log

时间秒杀一切 提交于 2019-12-13 11:44:50
问题 I got (in ITC) below presented crash report for my first Mac App Store app. Using knowledge founded on Stackoverflow I tried to symbolicate this log, but (using atos and otool) I was only able to read last (20) line (which means start (in My App) + 52 . I really don't know how to interpret lines above, and how to find cause of crash. Process: My App [270] Identifier: com.mycompany.myapp Version: 1.0.0 (1.0.0) App Item ID: 568750000 App External ID: 11410000 Code Type: X86-64 (Native) Parent

C# part of iOS crash log stack trace doesn't make any sense

南笙酒味 提交于 2019-12-11 04:53:18
问题 I have a crash log file that I symbolicate using information in the binary file. I verified that crash log is related to this particular binary. I'm even able to get out C#-level stack trace: $atos -arch armv7 -o 'dev.app'/'dev' 0x00156ac0 m_Action_Spin_MakeChips_Cell_double_double_ulong_System_Collections_Hashtable_System_Collections_Generic_List_1_Chip (in dev) + 1316 However, the stack trace I get that way doesn't make any sense! These methods don't call each other, and aren't related. May

How do I read an Xcode crash report?

十年热恋 提交于 2019-12-08 16:05:39
问题 I have an app that I just submitted it to the app sore (The app was developed for me as I do not know iOS development I do however know know other coding languages). Apple rejected the app saying that is crashed (The strange thing is is never crashed in all tests I did, probably about 50!) I got their crash log, Symbolicated it in Xcode and get this as a result. The only problem is that I don't understand this either. I was wondering if someone can explain what this means, Where abouts in my

Unable to symbolicate crash log

不问归期 提交于 2019-12-08 13:28:53
问题 I am facing some problem in symbolicating my crash log. I followed all the steps as answered by naveenshan in this thread. But once I execute the line atos -arch armv7 -o 'app name.app'/'app name' 0x0003b508 , it just throws me back the address 0x0003b508 back on the console. I am not able to figure out why its not symbolicating my crash log. I even tried symbolicating by drag and drop my crash log into device logs in my xcode. But even that doesnt seem to work. 回答1: You have to have the

Symbolicate crash report without the app binary

天大地大妈咪最大 提交于 2019-12-08 01:36:24
问题 I'm investigating how to create a server side iOS crash report symbolication server like Crashlitics or Crittercism or HokeyApp, from I can see, they only ask the user to upload the .dSYM file then they are able to symbolicate the crash report, I'm wondering how they archive it? Apple's standard symbolicatecrash command needs the app binary and the .dSYM file being provided together: Symbolication - resolving stack trace addresses to source code methods and lines - requires the application

Execute symbolicatecrash from shell script

末鹿安然 提交于 2019-12-07 21:07:57
问题 I am trying to call symboliccrash from a shell script that loops through multiple crash log file and outputs symbolicated version, but it is failing with an error message saying "command not found" But it works fine in the command line. symboliccrash CRASH_FILE.crash APP.dSYM > symbolicated.crash I tried to find the source for symboliccrash but it fails to find it which -a symboliccrash Shell Script Code #!/usr/bin/bash export DEVELOPER_DIR="/Applications/Xcode.app/Contents/Developer" i=0 for