Nothing (reliably) helpful from atos + dSYM
Nothing (reliably) helpful from atos + dSYM
- Subject: Nothing (reliably) helpful from atos + dSYM
- From: Nathan Vander Wilt <email@hidden>
- Date: Thu, 20 Nov 2008 10:23:38 -0800
I recently sent out a release of an upcoming product to some alpha
testers, who found a few crashers. They sent me the crashlogs and
since I had generated dSYM info for the build, I gave atos a shot.
From the directory where I had both Mercatalog.app and
Mercatalog.app.dSYM, I tried:
/Developer/user/bin/atos -arch x86_64 -o Mercatalog.app/Contents/MacOS/
Mercatalog 0x0000000100020ff4
but all I got back was the almost-useless:
0x0000000100020ff4 (in Mercatalog)
I used dwarfdump --uuid to compare the UUIDs between the .dSYM and the
app executable and they matched.
I also tried using:
dwarfdump Mercatalog.app.dSYM --arch=x86_64 --lookup= 0x0000000100020ff4
but that didn't find anything either, although maybe I'm using that
wrong (It outputs "Looking up address: 0x00000000ffffffff in the debug
information...not found.", which isn't what I wanted it to look up
anyway...)
The odd thing is that I did get atos to work just fine (with the exact
same project.pbxproj) when I force a crash by adding a
printf((char*)1) to the otherwise unchanged source code. Why would it
work with the build I just made this morning, but not the copy of the
build I sent out last week? Does atos break if the executable/symbols
are moved from the original build path? I need a reliable way of
getting symbol information for released products.
thanks,
-natevw
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden