crash log and debug

hi, is it possible using a crash log inside a device determine the source position of exception?

is it possible using a crash log inside a device determine the source position of exception?

I suspect I'm missing the point here because the obvious answer is just too obvious: if you open a correctly symbolicated crash log the backtraces for the thread that crashed will show your the source position of the exception.

Share and Enjoy

Quinn "The Eskimo!"
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"

hi, can you help me for that? i have a crash log from ipad but i don't understand what point to check inside my source... crash log is in the customer ipad

{"app_name":"vanigliaprobetaios","app_version":"4.0","bundleID":"com.volpato.vanigliaprobetaios","adam_id":0,"os_version":"iPhone OS 8.4 (12H143)","slice_uuid":"44f7f8ce-2b0a-393d-b910-98de48f62213","share_with_app_devs":false,"build_version":"4.0","is_first_party":false,"bug_type":"109","name":"vanigliaprobetaios"}

Incident Identifier: 706920D6-FD6C-4E8C-88A3-488895B1B7FC

CrashReporter Key: fe2a6c1120b78505a2f2443939f7eda5f2e697f1

Hardware Model: iPad4,1

Process: vanigliaprobetaios [670]

Path: /private/var/mobile/Containers/Bundle/Application/F1840DAF-FA77-48A5-83F4-140CE2096EAF/vanigliaprobetaios.app/vanigliaprobetaios

Identifier: com.volpato.vanigliaprobetaios

Version: 4.0 (4.0)

Code Type: ARM-64 (Native)

Parent Process: launchd [1]


Date/Time: 2015-07-18 17:40:50.503 +0200

Launch Time: 2015-07-18 17:14:27.873 +0200

OS Version: iOS 8.4 (12H143)

Report Version: 105


Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Subtype: KERN_INVALID_ADDRESS at 0x00000000b6a9beb8

Triggered by Thread: 0


Thread 0 name: Dispatch queue: com.apple.main-thread

Thread 0 Crashed:

0 libobjc.A.dylib 0x0000000195583bd0 0x195568000 + 113616

1 CoreFoundation 0x0000000183af1454 0x183aec000 + 21588

2 QuartzCore 0x0000000187fc4ad4 0x187fb8000 + 51924

3 QuartzCore 0x0000000187fcaae8 0x187fb8000 + 76520

4 CoreFoundation 0x0000000183af1454 0x183aec000 + 21588

5 QuartzCore 0x0000000187fcd630 0x187fb8000 + 87600

6 libdispatch.dylib 0x0000000195bed950 0x195bec000 + 6480

7 libdispatch.dylib 0x0000000195bf2208 0x195bec000 + 25096

8 CoreFoundation 0x0000000183bcb7f4 0x183aec000 + 915444

9 CoreFoundation 0x0000000183bc989c 0x183aec000 + 907420

10 CoreFoundation 0x0000000183af52d0 0x183aec000 + 37584

11 GraphicsServices 0x000000018d3fb6f8 0x18d3f0000 + 46840

12 UIKit 0x00000001886f2f3c 0x18867c000 + 487228

13 vanigliaprobetaios 0x00000001001b34e4 0x100020000 + 1651940

14 libdyld.dylib 0x0000000195c1aa04 0x195c18000 + 10756


Thread 1 name: Dispatch queue: com.apple.libdispatch-manager

Thread 1:

0 libsystem_kernel.dylib 0x0000000195d18c24 0x195d18000 + 3108

1 libdispatch.dylib 0x0000000195bfde6c 0x195bec000 + 73324

2 libdispatch.dylib 0x0000000195bef998 0x195bec000 + 14744


Thread 2 name: com.apple.NSURLConnectionLoader

Thread 2:

0 libsystem_kernel.dylib 0x0000000195d18e0c 0x195d18000 + 3596

1 libsystem_kernel.dylib 0x0000000195d18c84 0x195d18000 + 3204

2 CoreFoundation 0x0000000183bcb720 0x183aec000 + 915232

3 CoreFoundation 0x0000000183bc9674 0x183aec000 + 906868

4 CoreFoundation 0x0000000183af52d0 0x183aec000 + 37584

5 CFNetwork 0x00000001835d2590 0x183534000 + 648592

6 Foundation 0x0000000184b15db4 0x184a20000 + 1007028

7 libsystem_pthread.dylib 0x0000000195dcfdc4 0x195dcc000 + 15812

8 libsystem_pthread.dylib 0x0000000195dcfd20 0x195dcc000 + 15648

9 libsystem_pthread.dylib 0x0000000195dccef4 0x195dcc000 + 3828


Thread 3 name: com.apple.CFSocket.private

Thread 3:

0 libsystem_kernel.dylib 0x0000000195d33498 0x195d18000 + 111768

1 CoreFoundation 0x0000000183bd1124 0x183aec000 + 938276

2 libsystem_pthread.dylib 0x0000000195dcfdc4 0x195dcc000 + 15812

3 libsystem_pthread.dylib 0x0000000195dcfd20 0x195dcc000 + 15648

4 libsystem_pthread.dylib 0x0000000195dccef4 0x195dcc000 + 3828


Thread 4 name: Dispatch queue: com.apple.root.default-qos

Thread 4:

0 QuartzCore 0x0000000187fc4ef0 0x187fb8000 + 52976

1 QuartzCore 0x0000000187fc5044 0x187fb8000 + 53316

2 QuartzCore 0x0000000187fc4dec 0x187fb8000 + 52716

3 QuartzCore 0x0000000187fc4d74 0x187fb8000 + 52596

4 libdispatch.dylib 0x0000000195bed950 0x195bec000 + 6480

5 libdispatch.dylib 0x0000000195bfa77c 0x195bec000 + 59260

6 libdispatch.dylib 0x0000000195bfbc48 0x195bec000 + 64584

7 libsystem_pthread.dylib 0x0000000195dcd228 0x195dcc000 + 4648

8 libsystem_pthread.dylib 0x0000000195dcceec 0x195dcc000 + 3820


Thread 5:

To start you need to symbolicate the crash log. For background on this, see TN2151 Understanding and Analyzing iOS Application Crash Reports.

IMPORTANT The advice in the technote for how to symbolicate a log is incorrect (we're in the process of updating the technote right now). I recently posted up-to-date instructions in a different thread.

Share and Enjoy

Quinn "The Eskimo!"
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"
crash log and debug
 
 
Q