iPhone SDK Simulator

March 28, 2009 § 1 Comment

This is another block of errors on Xcode Console. Your app fail on both iPhone simulator and device. However your Xcode shows no errors or warnings after Build and Debug.

Errors from Console:

WARNING: Falling back to active SDK directory at: /Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator2.2.sdk

Loading program into debugger…
GNU gdb 6.3.50-20050815 (Apple version gdb-963) (Sun Nov  2 03:13:07 UTC 2008)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type “show copying” to see the conditions.
There is absolutely no warranty for GDB.  Type “show warranty” for details.
This GDB was configured as “–host=i386-apple-darwin –target=arm-apple-darwin”.tty /dev/ttys000
warning: Unable to read symbols from “dyld” (prefix __dyld_) (not yet mapped into memory).
warning: Unable to read symbols from “Foundation” (not yet mapped into memory).
warning: Unable to read symbols from “UIKit” (not yet mapped into memory).
warning: Unable to read symbols from “CoreGraphics” (not yet mapped into memory).
warning: Unable to read symbols from “AudioToolbox” (not yet mapped into memory).
warning: Unable to read symbols from “AVFoundation” (not yet mapped into memory).
warning: Unable to read symbols from “QuartzCore” (not yet mapped into memory).
warning: Unable to read symbols from “CoreLocation” (not yet mapped into memory).
warning: Unable to read symbols from “libgcc_s.1.dylib” (not yet mapped into memory).
warning: Unable to read symbols from “libSystem.B.dylib” (not yet mapped into memory).
warning: Unable to read symbols from “libobjc.A.dylib” (not yet mapped into memory).
warning: Unable to read symbols from “CoreFoundation” (not yet mapped into memory).
Program loaded.
target remote-mobile /tmp/.XcodeGDBRemote-127-20
Switching to remote protocol
mem 0x1000 0x3fffffff cache
mem 0x40000000 0xffffffff none
mem 0x00000000 0x0fff none
sharedlibrary apply-load-rules all

It happened to me. I found no errors. I repeatedly remove block of codes and UIButtons on Interface Builder, then recreate the code blocks and UIButtons from scratch. Renaming the problematic UIbutton names and methods that fail the console won’t help. Restarting computer and Xcode won’t help. Restoring the device won’t help.

How did I end up there. I was working on recording and playing music via Audio Queue Services,. I learn that it is a very bad idea to add such feature on top of existing app. Even it didn’t add any errors and warning, it corrupted simulator and device overloading the buffer on simulator and device. Restarting and restoring device won’t remove these overloaded buffer. As soon as I remove all the threads from Audio Queue Services, warning on Simulator Console related to UUID will disappear.

WARNING: Falling back to active SDK directory at: /Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS2.2.sdk

warning: UUID mismatch detected with the loaded library – on disk is:
/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS2.2.sdk/System/Library/Frameworks/Foundation.framework/Foundation
=uuid-mismatch-with-loaded-file,file=”/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS2.2.sdk/System/Library/Frameworks/Foundation.framework/Foundation”

….

Approach:
If you have a UIAction method containing multiple tasks, it is best if you comment out each small block of codes using /* … your code …. */. Build it on the console and see which small block of codes give you the above error.

The simulator error on console warning: Unable to read symbols from “dyld” (prefix __dyld_) (not yet mapped into memory). may refer to how Xcode fails to recognize your code. If you have been making many changes on the same block of codes especially you have moved the UIButton around on InterfaceBuilder or you have made many slight changes on UIButton, Xcode will break.

You may not see any syntax error or warning on Xcode. However it will fail on simulator and it will display the errors on Console.

After spending hours and hours in troubleshooting block of codes that are working at some point and fail later with no good explanation, I discover the simple recovery is to just type the same code again.

Again this is a very common errors most iPhone developers quoted. I find out how to resolve and narrow the sources of problems after hours and hours of investigation. It certainly deserves to mention them.

Advertisements

§ One Response to iPhone SDK Simulator

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

What’s this?

You are currently reading iPhone SDK Simulator at Web Builders.

meta

%d bloggers like this: