What is best way to symbolicated such crash log on recently iOS 15.X

Hi All, Since iOS 15.x, We don't need to take .dsym file to parse the crash, and it is readable, but hard to understand.

such crash signature:

"vmSummary" : "ReadOnly portion of Libraries: Total=840.5M resident=0K(0%) swapped_out_or_unallocated=840.5M(100%)\nWritable regions: Total=603.5M written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=603.5M(100%)\n\n VIRTUAL REGION \nREGION TYPE SIZE COUNT (non-coalesced) \n=========== ======= ======= \nActivity Tracing 256K 1 \nCG raster data 144K 3 \nColorSync 48K 3 \nCoreAnimation 416K 12 \nFoundation 16K 1 \nImage IO 3696K 10 \nKernel Alloc Once 32K 1 \nMALLOC 593.4M 101 \nMALLOC guard page 192K 12 \nSQLite page cache 256K 4 \nSTACK GUARD 240K 15 \nStack 9008K 27 \nVM_ALLOCATE 176K 3 \n__AUTH 4558K 481 \n__AUTH_CONST 25.0M 632 \n__DATA 18.4M 632 \n__DATA_CONST 25.5M 638 \n__DATA_DIRTY 2729K 531 \n__FONT_DATA 4K 1 \n__LINKEDIT 194.0M 14 \n__OBJC_CONST 6358K 441 \n__OBJC_RO 91.2M 1 \n__OBJC_RW 3488K 1 \n__TEXT 646.5M 660 \n__UNICODE 588K 1 \ndyld private memory 1024K 1 \nlibnetwork 128K 8 \nmapped file 194.9M 59 \nshared memory 48K 3 \n=========== ======= ======= \nTOTAL 1.8G 4297 \n", "legacyInfo" : { "threadTriggered" : { "queue" : "com.apple.root.user-initiated-qos" } },

How to interpret such crash log, and what is best way to catch or debug, just enable Zombie or something else?

Thanks

VCS-2022-02-01-162044.log
Up vote post of Jeff Lu Down vote post of Jeff Lu
1.9k views
Posted by
Jeff Lu
Reply
Add a Comment

Replies

You should use the standard symbolication path in Xcode. I see there's a few symbol names from your app that are missing; even if that wasn't the case, using the standard Xcode process will format the log into a different format that is more human readable.

Posted by
edford
Up vote reply of edford Down vote reply of edford
Add a Comment

Thanks @edford.

My issue is that (my app generated since 2007 by Objective C ) on old iOS (prior to iOS 15.x), I can find the crash file with XXXX.crash or XXXX.ips.beta, and update the name to .crash, download .dsym file to parse the crash file by Xcode,

since iOS 15.x, at least on my team side, there is no ***.crash or xxxx.ips.beta file when crash occurred. attached file was on iOS 15.x device when app was crashed, I have no idea how to take old school way to parse those crash log.

if I take the old school to change the extension name from .log to .crash Xcode does not accept those file at all when I drag to device logs panel.

Best regards.

Posted by
Jeff Lu
Up vote reply of Jeff Lu Down vote reply of Jeff Lu

  • Make sure you're using the latest Xcode version (Xcode 13.2.1 or Xcode 13.3 beta 2). Some earlier versions of Xcode 13 did not correctly accept the crash logs, and that is addressed in these versions.

    —
    edford
Add a Comment

Thanks @edford, I have downloaded Xcode13.3 beta 2, and trying to drag and drop the crash file into Xcode device logs Panel, no luck on my side.

it does not accept at all.

VCS-2022-02-08-153814.log

VCS-2022-02-08-094833.log
Posted by
Jeff Lu
Up vote reply of Jeff Lu Down vote reply of Jeff Lu

  • Let me be a little more specific in my prior response -- Xcode 13.3 beta 2 will be able to symbolicate these logs using the drag and drop technique to the Devices Organizer described in the documentation that I linked to above. That means the crash reports have the .crash file extension before dragging to Xcode. I can see the ones posted here have the .log file extension. I apologize for not being more specific on that!

    —
    edford
Add a Comment

@edford, thanks for your patient, I come back to close my thread here, I got it solved on this link: Problem solved

Posted by
Jeff Lu
Up vote reply of Jeff Lu Down vote reply of Jeff Lu
Add a Comment