iphone - Force symbolicatecrash to use a specific .app and .dSYM file? -
iphone - Force symbolicatecrash to use a specific .app and .dSYM file? -
i have .crash log ad-hoc version of app symbolicatecrash refuses symbolicate. have applied .patch remove 'die' command in symbolicatecrash after apple broke script in xcode 3.2.6. symbolicatecrash has worked other crash logs refuses symbolicate one. advertisement hoc app built , stored in "archived applications", there no reason why xcode shouldn't able find it. have copied .app , .dsym files right next .crash log, no dice.
is there way can forcefulness symobolicatecrash utilize specific .app , .dsym files if doesn't think applies?
turns out accidentally deleted build associated crash log. symbolicatecrash uses next logic figure out if there symbols associated crash log:
at bottom of every crash log list of binary images. yours listed first. there guid associated binary image. example:
0x1000 - 0x2befff +myapp armv7 <a95274a309d73458a40cb5a6fd317a1c> /var/mobile/applications/91884634-da1a-4bdb-9e1e-6f487d8f25d7/myapp.app/myapp the relevant guid is: a95274a309d73458a40cb5a6fd317a1c
it next uses tool mdfind, looks @ metadata associated files in file system, uppercase , hyphenated form of guid.
from archived applications, if click on myapp.app.dsym, info, disclose more info, see dsym uuids , 2 guids listed. sec guid 1 relevant. of form:
a95274a3-09d7-3458-a40c-b5a6fd317a1c
provided sec guid matches guid in .crash file, symbolicate crash able find , symbolicate. if don't match, it's wrong binary.
cheers, eric
iphone xcode symbols symbolicatecrash
Comments
Post a Comment