symbolicate

问题 A customer sent me a crash log from an iOS 5.0.1 (9A405) device. I'm running Xcode 4.2 on Snow Leopard. The system parts of the crash log call stack fail to symbolicate, and it seems that they're relevant to the crash; there are no iOS 5.0.1 symbols in Xcode. I don't have a 5.0.1 device, and I don't think I can install it, now that 5.1 is the latest. Is there a way for force-download symbols for a given iOS version in Xcode without plugging in a device? EDIT: seems like you can force a

问题 Excuse me! There's a problem confuse me! I have the Myapp.app.dSYM. (All Symbols has stripped from the MyApp.app and copy to dSYM) Now I use symbolicatecrash tool to symbolicate Crashes, it's not working! Hex address is still there. Part of my crash log: ...... 11 MyApp 0x00000001010ac2c8 0x100070000 + 17023688 12 MyApp 0x00000001010b1168 0x100070000 + 17043816 13 MyApp 0x00000001010b10e0 0x100070000 + 17043680 ...... So I try to use: atos -arch arm64 -o MyApp.app.dSYM/Contents/Resources

问题 i have these crash logs and after i drop them in the organizer the get symbolicated automatically but the result is always the same. the iOS calls get symbolicated and my app calls don't. I tried copying the dysm and app file into the same folder, deleting and copying back again. nothing helped. Any idea whats going on ? So I am getting something like this: Last Exception Backtrace: 0 CoreFoundation 0x36d4088f __exceptionPreprocess + 163 1 libobjc.A.dylib 0x31071259 objc_exception_throw + 33

问题 My app got rejected from Apple and I have got crash reports in .txt format instead of .crash format. How can I symbolicate or read the crash report ? 回答1: When you get your crash report as a .txt file just follow these steps : Change the file extension .txt to .crash (eg mycrash.txt to mycrash.crash ). Create a new folder in desktop and copy the mycrash.crash file to the newly created folder. Copy the .dSYM file: update: download all DSYMs from appstoreconnect activity- they are properly

问题 I received a crash report via AirBrake.io that isn't symbolicated. Since the crash report is not in exactly the same format as an Apple crashlog I can't just drop it on XCode as usual, so I took the exact same build from my XCode archive tried to symbolicate it on the commandline. With the following result: $ atos -o kidsapp.app/kidsapp 0x0002fc4c 0x0002fc4c (in kidsapp) I'm absolutely sure I'm using the same build as the crash report is from. So I also tried with dwarfdump: $ dwarfdump -

问题 Apple indicates the app crashes at launch on iphone 5, but I can't see where. On my iPhone 5 and iPad it runs perfectly. This is the Apple notes and crash report (it's symbolicated on organizer and manually-I think-). Please help me to inspect what seems to be the problem. Apple notes: We found that your app crashed upon launch on iPhone 5 running iOS 6.1.4, which is not in compliance with the App Store Review Guidelines. This occurred when your app was used: On Wi-Fi On cellular network We

问题 How to I get to symbolicate everything? Here is an example so what I am talking about: Thread 0 name: Dispatch queue: com.apple.main-thread Thread 0 Crashed: 0 CoreFoundation 0x351642cc CFRelease + 32 1 CoreFoundation 0x3518e130 CFArraySetValueAtIndex + 284 2 AddressBook 0x32971aba ABCMultiValueReplaceLabel + 58 3 AddressBook 0x3298c598 ABMultiValueReplaceLabelAtIndex + 140 4 My App 0x00011206 0x00011206 5 My App 0x00010e48 0x00010e48 6 My App 0x00011ada 0x00011ada 7 My App 0x0001027c

问题 I have an app on the App Store that is crashing. I have tried several of the solutions on SO to symbolicate my app, using at different times the Organizer, the Terminal, and Instruments. Nothing has worked so far - the lines in the reports from the methods in my app are never symbolicated, even when the lines for Apple methods are. After looking around for a while, it seems as though this might have something to do with the app name, which is along the lines of "Angie's List" - with both an

问题 I want to symbolicate the stack trace symbols logged using [NSThread callStackSymbols] to identify the full stack backtrace calls. But, this doesn't give symbolicated trace. 0 TestApp 0x0029616f TestApp + 1823087 1 TestApp 0x003ef18d TestApp + 3236237 2 UIKit 0x2ab7bb1f <redacted> + 438 3 UIKit 0x2ac0bea3 <redacted> + 306 4 UIKit 0x2ab7bb1f <redacted> + 438 5 CoreFoundation 0x2757546d <redacted> + 48 6 CoreFoundation 0x2756e4c3 <redacted> + 234 7 UIKit 0x2ab7bc9b <redacted> + 818 8 UIKit

问题 I have spend couple of days lately to learn how to symbolicate a line number of a crash which I receive with a custom solution. I have figure out I need the .app and .dSYM files, I have checked the UUID and it's the same as the crash that I get, where I also get the UUID to validate. Three identical UUID and the architecture is arm64, I get the crash to test it from my iPhone5S. OK, let's say I have in my stacktrace two related to my application lines. Here is the full stacktrace from the