A user of our app sent me the following crash log (already symbolicated):
Incident Identifier: 59D4D5E7-570A-4047-A679-3016B2A226C4
CrashReporter Key: d8284d671ee22ad17511360ce73409ebfa8b84bb
Process: .... [63]
Path: /var/mobile/Applications/....
Identifier: ...
Version: ??? (???)
Code Type: ARM (Native)
Parent Process: launchd [1]
Date/Time: 2010-03-08 17:00:15.437 -0800
OS Version: iPhone OS 2.2.1 (5H11a)
Report Version: 103
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x00000001, 0xe7ffdefe
Crashed Thread: 0
Thread 0 Crashed:
0 dyld 0x2fe01060 dyld_fatal_error + 0
1 dyld 0x2fe088d4 dyld::_main(mach_header
const*, unsigned long, int, char const**, char const**, char const**)
+ 3064
2 dyld 0x2fe0196c
dyldbootstrap::start(mach_header const*, int, char const**, long) +
884
3 dyld 0x2fe01048 _dyld_start + 32
Thread 0 crashed with ARM Thread State:
r0: 0x2fe23ca0 r1: 0x00000000 r2: 0x2fe23ca0 r3:
0x00000000
r4: 0x2ffff4e0 r5: 0x2ffff4bc r6: 0x2fe005c0 r7:
0x2ffffb00
r8: 0x00000004 r9: 0x2fe57cf0 r10: 0x2fe236c8 r11:
0x00000009
ip: 0x0000018d sp: 0x2ffff5b8 lr: 0x2fe088dc pc:
0x2fe01060
cpsr: 0x00000010
Binary Images:
0x2fe00000 - 0x2fe22fff dyld ??? (???)
<f6a50d5f57a676b54276d0ecef46d5f0> /usr/lib/dyld
My app uses OpenFeint and PinchMedia analytics. For PinchMedia, I'm linking using their provided .a file, and for OpenFeint, I'm compiling their code (as per their guidelines).
The frameworks / libs I'm linking are:
UIKit.framework (Weak)
MapKit.framework (Weak)
Foundation.framework
CoreGraphics.framework
OpenAL.framework
AudioToolbox.framework
libsqlite3
SystemConfiguration.framework
CoreLocation.framework
PinchMedia analytics
Security.framework
QuartzCore.framework
CFNetwork.framework
My base SDK is iPhone 3.0, and my Base OS Deployment Target is 2.2.1.
There are two things I find weird:
The app crashes even before the main method is invoked.
The crash log looks exactly like the one posted here: Objective-C iPhone App EXC_BREAKPOINT (SIGTRAP)
The user that sent me this crash is using a 2nd gen iPod Touch with OS 2.2.1. I wasn't able to reproduce the issue, but based on the comments in iTunes, it seems that more people is having the same issue.
I had the exact same problem. Solution: Weak link UIKit.framework
Related
I have reported this error to Apple a couple times and still have had no luck getting help so maybe someone here can help...
First off when beginning an app using swift all my syntax is white, which I have looked into this from these threads below: Error Xcode 6 --> Error SourceKit terminated. Editor functionality temporarily limited
and still no luck...?!
Still every time I try to run the app in the simulator xcode crashes and gives me the below info in the bug report.
It appears that thread 13 is the issue but I have no idea what the specific issue is or how to fix it...(if you need more info let me know).
Any help with this or any direction to find help would be immensely appreciated.
Thank you!
Bug report info:
Process: Xcode [374]
Path: /Applications/Xcode.app/Contents/MacOS/Xcode
Identifier: com.apple.dt.Xcode
Version: 6.3.2 (7718)
Build Info: IDEFrameworks-7718000000000000~2
App Item ID: 497799835
App External ID: 812404257
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Xcode [374]
User ID: 501
Crashed Thread: 13 Dispatch queue: com.apple.root.default-qos
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000010
VM Regions Near 0x10: -->
__TEXT 000000010fde7000-000000010fde8000 [ /Applications/Xcode.app/Contents/MacOS/Xcode
Thread 13 Crashed:: Dispatch queue: com.apple.root.default-qos
0 com.apple.DVTiPhoneSimulatorRemoteClient 0x00000001157b2165 __59-[SimDevice(DVTAdditions)
dvt_notifyOfBootOnQueue:handler:]_block_invoke + 326
1 libdispatch.dylib 0x00007fff8e654b15 _dispatch_call_block_and_release + 12
2 libdispatch.dylib 0x00007fff8e6511b2 _dispatch_client_callout + 8
3 libdispatch.dylib 0x00007fff8e65378c _dispatch_root_queue_drain + 838
4 libdispatch.dylib 0x00007fff8e65e848 _dispatch_worker_thread3 + 71
5 libsystem_pthread.dylib 0x00007fff8b8d7bd1 _pthread_wqthread + 663
6 libsystem_pthread.dylib 0x00007fff8b8d5a01 start_wqthread + 13
Thread 13 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000000 rbx: 0x0000000000000337 rcx: 0x000000000000000d rdx:0x000000012486cd78
rdi: 0x0000000000000000 rsi: 0x0000000000000000 rbp: 0x000000012486ce50 rsp:0x000000012486ce10
r8: 0x00000000000007ff r9: 0x00007f92761575d0 r10: 0x00007f92732f7ab0
r11: 0x00007fff753f4ef0
r12: 0x00007f92761575d0 r13: 0x00007fff85573a10 r14: 0x00007f92785b5430 r15: 0x00007f9279a0f180 rip: 0x00000001157b2165 rfl: 0x0000000000010206 cr2: 0x0000000000000010
Logical CPU: 0
Error Code: 0x00000004
Trap Number: 14
Sorry for my stupid question, but I just don't get eclipse juno running...
Here the error report:
Process: eclipse [10355] Path:
/Applications/eclipse/Eclipse.app/Contents/MacOS/eclipse Identifier:
eclipse Version: ??? (???) Code Type: X86-64 (Native)
Parent Process: bash [10309]
Date/Time: 2012-09-10 23:11:26.871 +0100 OS Version: Mac OS
X 10.7.4 (11E53) Report Version: 9
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes:
KERN_INVALID_ADDRESS at 0x000000000000003c
VM Regions Near 0x3c:
-->
__TEXT 0000000100000000-0000000100004000 [ 16K] r-x/rwx SM=COW
/Applications/eclipse/Eclipse.app/Contents/MacOS/eclipse
Application Specific Information: objc[10355]: garbage collection is
OFF
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0
com.apple.CoreFoundation 0x00007fff8d0f7aef
CFBundleGetFunctionPointerForName + 31 1 eclipse
0x00000001000030bd findSymbol + 66 2 eclipse
0x00000001000018be original_main + 1572 3 eclipse
0x0000000100001f7d main + 1230 4 eclipse
0x0000000100001158 start + 52
Thread 1:: Dispatch queue: com.apple.libdispatch-manager 0
libsystem_kernel.dylib 0x00007fff8fd6e7e6 kevent + 10 1
libdispatch.dylib 0x00007fff8f90d78a _dispatch_mgr_invoke
+ 923 2 libdispatch.dylib 0x00007fff8f90c31a _dispatch_mgr_thread + 54
Thread 0 crashed with X86 Thread State (64-bit): rax:
0xe1bfa23753d57bd3 rbx: 0x0000000100200ad0 rcx: 0x0000000000000000
rdx: 0x0000000000000000 rdi: 0x0000000000000000 rsi:
0x0000000100200ad0 rbp: 0x00007fff5fbff9b0 rsp: 0x00007fff5fbff590
r8: 0x000000000000000f r9: 0x000000000000000a r10:
0x0000000000064000 r11: 0x00007fff8d0f7ad0 r12: 0x00000001000043f8
r13: 0x00000001002007f0 r14: 0x00007fff5fbffbc8 r15:
0x00007fff5fbffbc8 rip: 0x00007fff8d0f7aef rfl: 0x0000000000010206
cr2: 0x000000000000003c Logical CPU: 1
Part removed ...
External Modification Summary: Calls made by other processes
targeting this process:
task_for_pid: 1
thread_create: 0
thread_set_state: 0 Calls made by this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0 Calls made by all processes on this machine:
task_for_pid: 16727
thread_create: 7
thread_set_state: 10414
VM Region Summary: ReadOnly portion of Libraries: Total=140.5M
resident=68.1M(49%) swapped_out_or_unallocated=72.3M(51%) Writable
regions: Total=29.1M written=424K(1%) resident=644K(2%)
swapped_out=0K(0%) unallocated=28.5M(98%) REGION TYPE
VIRTUAL
=========== ======= MALLOC 20.3M MALLOC guard page 32K STACK GUARD 56.0M Stack 8712K VM_ALLOCATE 32K
__CI_BITMAP 80K
__DATA 12.1M
__IMAGE 528K
__LINKEDIT 47.8M
__TEXT 92.7M
__UNICODE 544K shared memory 308K
=========== ======= TOTAL 238.9M
It would be great if anybody could help me.
Thank you very much for your help.
Greetings
Anselm
found the problem... I used Unarchiver to unpack the pack... It seems to have a bug... When I used another program to unpack it it worked :-)
here the eclipse link as reference: https://bugs.eclipse.org/bugs/show_bug.cgi?id=305758
How could I locate the crash code from the crash log in my ip4 device? As the crashed thread 0 presents a serial frameworks and main.m, I couldn't locate the accurate code launched this crash and debug it. Any suggestion? Thanks in advance!
Incident Identifier: B6BD84B7-CE0A-485D-A877-0FD0F5B75933
CrashReporter Key: b0b97a37f2a1e4911ce2ef34e1793e028463bb67
Hardware Model: iPhone3,1
Process: myApp [11615]
Path: /var/mobile/Applications/28AE71F2-36CA-4A87-83D9-07DF2DFE74F1/myApp.app/myApp
Identifier: myApp
Version: ??? (???)
Code Type: ARM (Native)
Parent Process: launchd [1]
Date/Time: 2012-06-09 21:12:22.792 +0800
OS Version: iPhone OS 5.1 (9B176)
Report Version: 104
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000b
Crashed Thread: 0
Thread 0 name: Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0 libobjc.A.dylib 0x36721f78 0x3671e000 + 16248
1 MapKit 0x34e7ace6 0x34e68000 + 77030
2 CoreFoundation 0x3525f1f4 0x35247000 + 98804
3 Foundation 0x311b6740 0x31112000 + 673600
4 CoreFoundation 0x352d4acc 0x35247000 + 580300
5 CoreFoundation 0x352d4298 0x35247000 + 578200
6 CoreFoundation 0x352d303e 0x35247000 + 573502
7 CoreFoundation 0x3525649e 0x35247000 + 62622
8 CoreFoundation 0x35256366 0x35247000 + 62310
9 GraphicsServices 0x36552432 0x3654e000 + 17458
10 UIKit 0x3234ce76 0x3231b000 + 204406
11 myApp 0x0001bac0 main (main.m:16)
12 myApp 0x0001ba80 start + 32
Is this the most recent version of your code that is crashing or a previous installed version?
If you are archiving your builds, you should be able to resymbolicate them via the XCode organizer. I think the most important thing is that you have a .dSYM files handy on your development machine for any builds you have installed on your various devices.
Here's a bit of Apple information on how to analyze crash reports.
Here is also a very related question here on StackOverflow that may help you out.
Does compiling with the iOS 4.3 SDK remove the support for the iPhone 3G and 2nd generation iPod touch devices?
After upgrading, I found that the ad-hoc and distribution builds no longer run on those devices, but installing the iOS 4.2 SDK to another directory, and performing no changes to the code or build settings, it does work correctly.
The application produces a crash report like the following:
OS Version: iPhone OS 3.0 (7A341)
Report Version: 104
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x00000000
Crashed Thread: 0
Thread 0 Crashed:
0 libobjc.A.dylib 0x3014579c 0x3000c000 + 1283996
Thread 1:
0 libSystem.B.dylib 0x31d47158 mach_msg_trap + 20
1 libSystem.B.dylib 0x31d49ed8 mach_msg + 60
2 CoreFoundation 0x3025454e CFRunLoopRunSpecific + 982
3 CoreFoundation 0x30254164 CFRunLoopRunInMode + 44
4 WebCore 0x3588dbc8 RunWebThread(void*) + 412
5 libSystem.B.dylib 0x31d705a0 _pthread_body + 20
Thread 0 crashed with ARM Thread State:
r0: 0x00000000 r1: 0x00000000 r2: 0x39d4a928 r3: 0x00000113
r4: 0x00114940 r5: 0x3893b29c r6: 0x38204d80 r7: 0x0031acf0
r8: 0x00000000 r9: 0x00000001 r10: 0x00000000 r11: 0x00000000
ip: 0x39d802b8 sp: 0x2fffee10 lr: 0x3000852c pc: 0x3014579c
cpsr: 0x80000010
As can be seen, there is not a single reference in the stack trace to the actual application, and there are only the two threads running.
Is it documented anywhere that compiling for those older devices has been dropped? Is there any way to add some kind of build setting so that it does remain functional on those devices moving forward?
iOS 4.3 is not supported on devices older than iPhone 3GS and iPod Touch 3rd Gen (excluding the 8GB model, which is also not supported).
Source: Apple.com (scroll to bottom)
I am setting up an Android environment for the first time on Eclipse. I have many years of Eclipse experience, but new to Android. This is being done on an Apple Mac Mini, running MacOSX 10.6.3. I am using the latest Eclipse Classic, version 3.5.2. I am trying to get the tiny hello world program running.
When I run it, I get the following in the console window of Eclipse:
[2010-06-12 13:48:08 - HelloAndroid] Automatic Target Mode: launching new emulator with compatible AVD 'Android2.2AVD'
[2010-06-12 13:48:08 - HelloAndroid] Launching a new emulator with Virtual Device 'Android2.2AVD'
[2010-06-12 13:48:11 - HelloAndroid] New emulator found: emulator-5554
[2010-06-12 13:48:11 - HelloAndroid] Waiting for HOME ('android.process.acore') to be launched...
[2010-06-12 13:48:12 - Emulator] 2010-06-12 13:48:12.783 emulator[50495:903] Warning once: This application, or a library it uses, is using NSQuickDrawView, which has been deprecated. Apps should cease use of QuickDraw and move to Quartz.
[2010-06-12 13:48:19 - HelloAndroid] emulator-5554 disconnected! Cancelling 'com.example.helloandroid.HelloAndroid activity launch'!
The emulator crashes with the following info.
I have followed all the instructions for running the hello world sample.
Anyone have any ideas?
Process: emulator [50398]
Path: /Users/jeremy/android-sdk-mac_86/tools/emulator
Identifier: emulator
Version: ??? (???)
Code Type: X86 (Native)
Parent Process: eclipse [50388]
Date/Time: 2010-06-12 13:28:38.595 -0400
OS Version: Mac OS X 10.6.3 (10D573)
Report Version: 6
Interval Since Last Report: 363037 sec
Crashes Since Last Report: 9
Per-App Crashes Since Last Report: 7
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000007fd000
Crashed Thread: 4
Thread 0: Dispatch queue: com.apple.main-thread
0 emulator 0x000eed4e helper_set_cp15 + 30
Thread 1:
0 libSystem.B.dylib 0x9020bbd2 __workq_kernreturn + 10
1 libSystem.B.dylib 0x9020c168 _pthread_wqthread + 941
2 libSystem.B.dylib 0x9020bd86 start_wqthread + 30
Thread 2: Dispatch queue: com.apple.libdispatch-manager
0 libSystem.B.dylib 0x9020cb42 kevent + 10
1 libSystem.B.dylib 0x9020d25c _dispatch_mgr_invoke + 215
2 libSystem.B.dylib 0x9020c719 _dispatch_queue_invoke + 163
3 libSystem.B.dylib 0x9020c4be _dispatch_worker_thread2 + 240
4 libSystem.B.dylib 0x9020bf41 _pthread_wqthread + 390
5 libSystem.B.dylib 0x9020bd86 start_wqthread + 30
Thread 3:
0 libSystem.B.dylib 0x901e635a semaphore_timedwait_signal_trap + 10
1 libSystem.B.dylib 0x90213ea1 _pthread_cond_wait + 1066
2 libSystem.B.dylib 0x90242a28 pthread_cond_timedwait_relative_np + 47
3 com.apple.audio.CoreAudio 0x9056f965 CAGuard::WaitFor(unsigned long long) + 219
4 com.apple.audio.CoreAudio 0x90572997 CAGuard::WaitUntil(unsigned long long) + 289
5 com.apple.audio.CoreAudio 0x90570294 HP_IOThread::WorkLoop() + 1892
6 com.apple.audio.CoreAudio 0x9056fb2b HP_IOThread::ThreadEntry(HP_IOThread*) + 17
7 com.apple.audio.CoreAudio 0x9056fa42 CAPThread::Entry(CAPThread*) + 140
8 libSystem.B.dylib 0x90213a19 _pthread_start + 345
9 libSystem.B.dylib 0x9021389e thread_start + 34
Thread 4 Crashed:
0 emulator 0x00040380 audioInDeviceIOProc + 96
Thread 4 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0x007fd000 ecx: 0x000001fe edx: 0x0198f3f0
edi: 0x00000200 esi: 0x01119850 ebp: 0x01119800 esp: 0xb020fad0
ss: 0x0000001f efl: 0x00010212 eip: 0x00040380 cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x0000001f gs: 0x00000037
cr2: 0x007fd000
I had this exact same problem just now, and when I googled around a bit, I found some threads where people mentioned using Logitech USB headsets, and that unplugging those headsets made the problem go away.
I have a Logitech USB desktop microphone, and sure enough, after unplugging it, the problem went away for me, too. Even though the mic was turned off the whole time!
Having connected the Apple LED Cinema Display, just setting audio input to internal solved the problem for me - no need to set external audio playback aside.