Skip to content

EXC_BAD_ACCESS on device #4

@markrickert

Description

@markrickert

So I'm trying to get this up and running on a device and I'm running into an EXC_BAD_ACCESS error when running in debug mode (it just stops with no error message when not in debug mode). Any idea about what's going on here?

$ rake device debug=1

  packet: QSetEnableAsyncProfiling;enable:1;interval_usec:1000000;scan_type:0xfffffeff;
response: OK
Process 0 connected
Executing commands in '/var/folders/v7/vrn4z9cs6ml0q2817kx3vrnh0000gn/T/_deploylldbcmds'.
(lldb)  command script import /var/folders/v7/vrn4z9cs6ml0q2817kx3vrnh0000gn/T/_deploylldbcmds.py
Process 194 stopped
* thread #1: tid = 0x14c7, 0x2bea9028 dyld`_dyld_start, stop reason = signal SIGSTOP
    frame #0: 0x2bea9028 dyld`_dyld_start
dyld`_dyld_start:
-> 0x2bea9028:  mov    r8, sp
   0x2bea902c:  sub    sp, sp, #0x10
   0x2bea9030:  bic    sp, sp, #0x7
   0x2bea9034:  ldr    r3, [pc, #112]            ; _dyld_start + 132
(lldb) c
Process 194 resuming
"Starting IAP"
2014-06-30 21:25:05.292 MYApp[194:60b] Starting purchase process.
Process 194 stopped
* thread #1: tid = 0x14c7, 0x3a2b5622 libobjc.A.dylib`objc_msgSend + 2, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x4)
    frame #0: 0x3a2b5622 libobjc.A.dylib`objc_msgSend + 2
libobjc.A.dylib`objc_msgSend + 2:
-> 0x3a2b5622:  ldr.w  r9, [r0]
   0x3a2b5626:  ldrh.w r12, [r9, #12]
   0x3a2b562a:  ldr.w  r9, [r9, #8]
   0x3a2b562e:  and.w  r12, r12, r1

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions