Iphone crash log with dSym not loading debug info
I was trying to figure out why my application crashed on device (iPhone) with dSym generated along the executable (in ad hoc), but I don't know why, there is no useful information. It seems like Organizer can find the corresponding dSym and translate some data into more readable data, but when it comes to my application, I just have the address.
Since I know how to reproduce it, I tried to tweak my build to help me in the future. So I was trying to find if I had all the relevant flags set in the project's build properties and everything seems fine. Therefore, after some research, it seems that all information gets deleted during linking and dSym seems completely useless. I've played with some flags but nothing has changed.
So, is there something special to make the crash file human readable? Or is it not possible in a special situation? The closest thing to what I did was build a debug version and find the address in it. At least it seems to give the correct file. So I made a sample application and this is what I have: (the line I want is # 4):
Thread 0 Crashed:
0 libobjc.A.dylib 0x00003ebc objc_msgSend + 20
1 UIKit 0x0005c970 -[UIView dealloc] + 60
2 UIKit 0x0005c840 -[UIImageView dealloc] + 76
3 CoreFoundation 0x0003963a -[NSObject release] + 28
4 MyApplication 0x000046a6 0x1000 + 13990
5 UIKit 0x00069750 -[UIViewController view] + 44
6 MyApplication 0x000053fa 0x1000 + 17402
The crash is done using two consecutive releases at the facility.
Thanks in advance.
a source to share
After many difficult attempts at getting debug information, I decided to create a new project from scratch and add everything back to it. And now it works great. It was probably some kind of hidden setting somewhere that was causing him to behave like this. I don't know what it was, and I'm still curious.
a source to share