Annoying Crashing Problem

Discussion in 'Mac Programming' started by simX, Jan 7, 2006.

  1. macrumors 6502a

    simX

    Joined:
    May 28, 2002
    Location:
    Bay Area, CA
    #1
    I've got a weird problem with a Cocoa app I'm developing. It works perfectly on Mac OS X 10.4, but when my friend runs it under Mac OS X 10.2, he gets this crash report:

    Code:
    Exception:  EXC_BAD_ACCESS (0x0001)
    Codes:      KERN_PROTECTION_FAILURE (0x0002) at 0x00000006
    
    Thread 0 Crashed:
     #0   0x90131df0 in CFRelease
     #1   0x97e201a4 in _decodeObjectBinary
     #2   0x97e4cad8 in -[NSKeyedUnarchiver _decodeArrayOfObjectsForKey:]
     #3   0x97e0c724 in -[NSArray initWithCoder:]
     #4   0x97e20328 in _decodeObjectBinary
     #5   0x97e284a4 in _decodeObject
     #6   0x930adfb0 in -[NSView initWithCoder:]
     #7   0x9314adf4 in -[NSCustomView initWithCoder:]
     #8   0x97e20328 in _decodeObjectBinary
     #9   0x97e284a4 in _decodeObject
     #10  0x930fdc4c in -[NSNibConnector initWithCoder:]
     #11  0x930f1444 in -[NSNibOutletConnector initWithCoder:]
     #12  0x97e20328 in _decodeObjectBinary
     #13  0x97e4cad8 in -[NSKeyedUnarchiver _decodeArrayOfObjectsForKey:]
     #14  0x97e0c724 in -[NSArray initWithCoder:]
     #15  0x97e20328 in _decodeObjectBinary
     #16  0x97e284a4 in _decodeObject
     #17  0x9314a354 in -[NSIBObjectData initWithCoder:]
     #18  0x97e20328 in _decodeObjectBinary
     #19  0x97e284a4 in _decodeObject
     #20  0x931b3cb4 in loadNib
     #21  0x930eaaa4 in +[NSBundle(NSNibLoading) _loadNibFile:nameTable:withZone:ownerBundle:]
     #22  0x9314a228 in +[NSBundle(NSNibLoading) loadNibFile:externalNameTable:withZone:]
     #23  0x93149fe8 in +[NSBundle(NSNibLoading) loadNibNamed:owner:]
     #24  0x93160570 in NSApplicationMain
     #25  0x00022614 in main
     #26  0x00002d4c in _start (crt.c:272)
     #27  0x00002bf0 in start
    
    Thread 1:
     #0   0x90073ba8 in mach_msg_trap
     #1   0x90005ed0 in mach_msg
     #2   0xc0009190 in __ape_internal
     #3   0xc0000efc in __ape_agent
     #4   0x90020c28 in _pthread_body
    
    PPC Thread State:
      srr0: 0x90131df0 srr1: 0x0200f030                vrsave: 0x00000000
       xer: 0x00000000   lr: 0x90131de0  ctr: 0x90131dc8   mq: 0x00000000
        r0: 0x97e201a4   r1: 0xbfffe840   r2: 0x28000242   r3: 0x00000000
        r4: 0x906ade3c   r5: 0x00000000   r6: 0x00000064   r7: 0x61726368
        r8: 0xa0131de0   r9: 0xa0131de0  r10: 0x00000000  r11: 0xa7df1618
       r12: 0x90131dc8  r13: 0x00000000  r14: 0x00000000  r15: 0xa309a288
       r16: 0x000cf4f0  r17: 0xa309a7c4  r18: 0xa309a288  r19: 0xa309a7c4
       r20: 0xa7defc68  r21: 0x000003fb  r22: 0x00000000  r23: 0x00201e50
       r24: 0x97f14ffc  r25: 0x00000000  r26: 0x0000852c  r27: 0x001e69b0
       r28: 0x00000000  r29: 0x00000000  r30: 0x00000000  r31: 0x90131de0
    The report seems to indicate that there's a problem in loading MainMenu.nib, but I can't seem to isolate the issue that is causing the crash. Does anybody have any insight into what could cause this? (I realize APE is in the crash report, and I just sent him an e-mail to disable it and try my app without that loaded.)
     
  2. macrumors 601

    HiRez

    Joined:
    Jan 6, 2004
    Location:
    Western US
    #2
    The first thing I would do is open your Nib files in IB and choose Compatibility Checking… from the File menu to see if anything in there is not compliant with 10.2.x. If so, you will have to replace or adjust those elements. Then check the project settings in Xcode to make sure you're compiling to be compatible with 10.2.x.
     
  3. thread starter macrumors 6502a

    simX

    Joined:
    May 28, 2002
    Location:
    Bay Area, CA
    #3
    Yeah, I'm aware of that -- there are only some minor problems, things like the "hidden" option in the Get Info panel, and the alternating table row colors aren't supported in 10.2 nibs.

    However, these have never caused crashes in my app before. My app should even work in 10.1 (there are more compatibility problems, but again, nothing that's ever caused a crash before). Something else is causing this crash problem.
     
  4. Guest

    caveman_uk

    Joined:
    Feb 17, 2003
    Location:
    Hitchin, Herts, UK
    #4
    Wait until he's uninstalled APE. All bets are off until that's gone.
     

Share This Page