debugging - XCode 4.6 crash report stacktrace only -
a customer send me crash log, contains stack trace. stack trace generated custom developed exception handler.
exception message: nsinvalidargumentexception exception reason: *** setobjectforkey: object cannot nil (key: pop_year) stacktrace: ( 0 corefoundation 0x3a9dc3ff <redacted> + 186 1 libobjc.a.dylib 0x39a35963 objc_exception_throw + 30 2 corefoundation 0x3a93e5ef <redacted> + 142 3 simplystats 0x0004640b simplystats + 103435 4 simplystats 0x000458e1 simplystats + 100577 5 simplystats 0x00034b83 simplystats + 31619 6 libdispatch.dylib 0x337c4793 <redacted> + 10 7 libdispatch.dylib 0x337c7b3b <redacted> + 142 8 libdispatch.dylib 0x337c567d <redacted> + 44 9 libdispatch.dylib 0x337c8613 <redacted> + 210 10 libdispatch.dylib 0x337c87d9 <redacted> + 92 11 libsystem_c.dylib 0x33cb67f1 <redacted> + 360 12 libsystem_c.dylib 0x33cb6684 start_wqthread + 8 )
this question has 2 parts:
can symbolicate partial crash log? (yes have .app , .dsym of actual file).
what must change in exception handler able import crash log future crash events?
edit: little more info; managed decoding of hex values using
atos -o simplystats.app/simplystats -arch armv7 0x00034b83
i did same more hexadecimal numbers. it's rather tedious! sure there must smarter way.
edit 2: since question gets no answers, best practice logging nsexceptions
, stacktraces in email message can analyzed?
Comments
Post a Comment