Crash logs filled with question marks

Discussion in 'Mac Basics and Help' started by Shookster, Oct 3, 2009.

  1. Shookster macrumors regular

    Joined:
    Feb 16, 2009
    #1
    Occasionally an application will crash and the crash log will be filled with question marks instead of the usual backtrace information.

    Does anyone know what causes this? It's quite rare but it has happened often enough for me to notice.

    Here's an example:
    Process: Final Cut Pro [5126]
    Path: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro
    Identifier: com.apple.FinalCutPro
    Version: 7.0 (7.0)
    Build Info: FCPApp-906181654~22
    Code Type: X86 (Native)
    Parent Process: launchd [828]

    Date/Time: 2009-09-28 21:25:31.481 +0300
    OS Version: Mac OS X 10.5.8 (9L31a)
    Report Version: 6
    Anonymous UUID: 7D611570-85E3-4E3B-9E71-F80BB6AB1F3E

    Exception Type: EXC_BAD_ACCESS (SIGBUS)
    Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000014
    Crashed Thread: 0

    Thread 0 Crashed:
    0 ??? 0x1fcead52 0 + 533638482
    1 ??? 0x138858b4 0 + 327702708
    2 ??? 0x1388102a 0 + 327684138
    3 ??? 0x00244d44 0 + 2379076
    4 ??? 0x00244eef 0 + 2379503
    5 ??? 0x00245288 0 + 2380424
    6 ??? 0x0024551e 0 + 2381086
    7 ??? 0x00245643 0 + 2381379
    8 ??? 0x004130d3 0 + 4272339
    9 ??? 0x04191648 0 + 68752968
    10 ??? 0x0419157e 0 + 68752766
    11 ??? 0x04191425 0 + 68752421
    12 ??? 0x06061981 0 + 101063041
    13 ??? 0x060bfd26 0 + 101448998
    14 ??? 0x060bfc77 0 + 101448823
    15 ??? 0x060bcf22 0 + 101437218
    16 ??? 0x0603713d 0 + 100888893
    17 ??? 0x0603657b 0 + 100885883
    18 ??? 0x060363e0 0 + 100885472
    19 ??? 0x06064d54 0 + 101076308
    20 ??? 0x060374f6 0 + 100889846
    21 ??? 0x0603657b 0 + 100885883
    22 ??? 0x06052ecc 0 + 101002956
    23 ??? 0x060bfa6c 0 + 101448300
    24 ??? 0x060bc2c2 0 + 101434050
    25 ??? 0x0015464f 0 + 1394255
    26 ??? 0x002c1aa8 0 + 2890408
    27 ??? 0x00003a6b 0 + 14955
    28 ??? 0x00003999 0 + 14745

    Thread 1:
    0 ??? 0x00c726fa 0 + 13051642
    1 ??? 0x00c54155 0 + 12927317
    2 ??? 0x00c54012 0 + 12926994

    Thread 2:
    0 ??? 0x00c2a46e 0 + 12756078
    1 ??? 0x00c54dcd 0 + 12930509
    2 ??? 0x0685ab32 0 + 109423410
    3 ??? 0x00c54155 0 + 12927317
    4 ??? 0x00c54012 0 + 12926994

    Thread 3:
    0 ??? 0x00c232e6 0 + 12727014
    1 ??? 0x00c552af 0 + 12931759
    2 ??? 0x00c56b33 0 + 12938035
    3 ??? 0x035bcdbc 0 + 56348092
    4 ??? 0x035bcbd0 0 + 56347600
    5 ??? 0x035bcb35 0 + 56347445
    6 ??? 0x028cb6e8 0 + 42776296
    7 ??? 0x03576dfd 0 + 56061437
    8 ??? 0x035769a4 0 + 56060324
    9 ??? 0x00c54155 0 + 12927317
    10 ??? 0x00c54012 0 + 12926994

    Thread 4:
    0 ??? 0x00c8c292 0 + 13157010
    1 ??? 0x00c8c2c2 0 + 13157058

    Thread 5:
    0 ??? 0000000000 0 + 0

    Thread 6:
    0 ??? 0x00c232ce 0 + 12726990
    1 ??? 0x00c552c6 0 + 12931782
    2 ??? 0x00c9a539 0 + 13215033
    3 ??? 0x0043ee7b 0 + 4451963
    4 ??? 0x00429495 0 + 4363413
    5 ??? 0x0046ac0c 0 + 4631564
    6 ??? 0x00c54155 0 + 12927317
    7 ??? 0x00c54012 0 + 12926994

    Thread 7:
    0 ??? 0x00c232ce 0 + 12726990
    1 ??? 0x00c552c6 0 + 12931782
    2 ??? 0x00c9a539 0 + 13215033
    3 ??? 0x0043ee7b 0 + 4451963
    4 ??? 0x004e5a4b 0 + 5134923
    5 ??? 0x0046ac0c 0 + 4631564
    6 ??? 0x00c54155 0 + 12927317
    7 ??? 0x00c54012 0 + 12926994

    Thread 8:
    0 ??? 0x00c23286 0 + 12726918
    1 ??? 0x00c2aa7c 0 + 12757628
    2 ??? 0x00ebde7e 0 + 15457918
    3 ??? 0x00ebeaa8 0 + 15461032
    4 ??? 0x011f85f8 0 + 18843128
    5 ??? 0x011f8480 0 + 18842752
    6 ??? 0x00c54155 0 + 12927317
    7 ??? 0x00c54012 0 + 12926994

    Thread 9:
    0 ??? 0x00c23286 0 + 12726918
    1 ??? 0x00c2aa7c 0 + 12757628
    2 ??? 0x00ebde7e 0 + 15457918
    3 ??? 0x00ebeaa8 0 + 15461032
    4 ??? 0x026ccecc 0 + 40685260
    5 ??? 0x026cf04c 0 + 40693836
    6 ??? 0x00c54155 0 + 12927317
    7 ??? 0x00c54012 0 + 12926994

    Thread 0 crashed with X86 Thread State (32-bit):
    eax: 0x00000000 ebx: 0x1388586c ecx: 0x00000000 edx: 0x00000001
    edi: 0x00000014 esi: 0x1388c55b ebp: 0xbfffef48 esp: 0xbfffef10
    ss: 0x0000001f efl: 0x00010282 eip: 0x1fcead52 cs: 0x00000017
    ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037
    cr2: 0x00000014

    Binary Images:
    0x8fe00000 - 0x8fe2f48b dyld 97.1 (???) <42823f3b2755e135abeb7f8ac838a1f8> /usr/lib/dyld
     
  2. ukelady macrumors newbie

    Joined:
    Mar 16, 2010
    #2
    Crash logs filled with question marks

    Hello,
    have you already found the cause of the question marks problem? I am having the same issue too...
     
  3. Shookster thread starter macrumors regular

    Joined:
    Feb 16, 2009
  4. wrldwzrd89 macrumors G5

    wrldwzrd89

    Joined:
    Jun 6, 2003
    Location:
    Solon, OH
    #4
    Applications that can't have their stack trace determined, for whatever reason, will cause this behavior. The stack trace contains, among other things, the functions that were called, in most recent to least recent order, which is useful for debugging.
     

Share This Page