IB Error: Unable to read symbols from "UIKit" (not yet mapped into memory)

Question

Level 1

0 points

IB Error: Unable to read symbols from "UIKit" (not yet mapped into memory)

I created a simple view program for iPhone, using IB to add a button and a label, once the button is clicked, the label text is changed.

I am able to compile it fine, and ran it. The program/view showed up. But when I clicked on the button, the console showed this message:

This GDB was configured as "i386-apple-darwin".warning: Unable to read symbols for "/System/Library/Frameworks/UIKit.framework/UIKit" (file not found).
warning: Unable to read symbols from "UIKit" (not yet mapped into memory).

I checked UIKit info, it's physically (full path) at:
/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS2.0.sdk/System/Lib rary/Frameworks/UIKit.framework

The relative path to SKD is:
System/Library/Frameworks/UIKit.framework

I'm running the latest SDK beta 8, OS X 10.5.4 latest update.

Anyone had this bizarre problem? I was able to run all Apple samples fine.

Please help!

THanks!

Mac Mini, Mac OS X (10.5.4)

Posted on Jul 13, 2008 5:40 AM

Reply

Answer 1

CodeShogun Author

Level 1

0 points

Jul 13, 2008 8:27 AM in response to CodeShogun

I downloaded the final SDK, same problem, even used absolute paths for the frameworks, anyone has any idea????

Reply

Answer 2

Jul 13, 2008 8:37 AM in response to CodeShogun

The frameworks are read from whatever the SDK is.

Make sure the SDK is set to iPhone Simulator.

If that doesn't work, make a new project and copy and paste your code into that. That's what solved it for me. But I was using an app that I had previously built with one of the earlier betas of the SDK.

Build settings in Xcode are so delicate, and impossible to fix once changed due to the myriad of choices none of which are adequately documented in plain English. And there is no way to "set all build settings back to what a new project would have" either.

You can also copy and paste objects in the XIB files from one project to another.

But I think the problem is that it is pointing to the wrong frameworks.

Reply

Answer 3

CodeShogun Author

Level 1

0 points

Jul 13, 2008 12:34 PM in response to johnnylundy

Thanks Johnny!

I was not able to resolve it by adding the correct UIKit.framework to my project.

I' using the View-Based application template.

later i used window-based application, and created the view myself, and seems no problem at all.

-< dont know what's going on, still learning :)</div>

Reply

Answer 4

gujamin

Level 4

1,099 points

Jul 27, 2008 9:29 AM in response to CodeShogun

I had a similar problem and I found that it was due to a breakpoint I had set. Try disabling or clearing all your breakpoints and see if that perhaps allows you to continue.

Reply

Answer 5

Dec 15, 2008 12:13 PM in response to CodeShogun

The answer is mentioned in a few other posts, but I thought I'd repeat it here, so that it's easier to find this solution in the future.

I got the same problem trying to build an iPhone-Simulator application using another build process -- in this case, Boost Build. When I tried to run the program, it gave me the same nonsensical dynamic-library error.

The problem is that the application you built for the iPhone Simulator is NOT a real application, even though it looks like one. You need to run it from within Xcode.

In my case, I got around the problem by building the GLPaint sample using Xcode, copying over the executable it generated with the one I generated via Boost Build, then running GLPaint (actually my program now) from within Xcode. Then it worked.

So far, it seems that Macintosh and iPhone are very unfriendly platforms to someone that's trying to port an existing project. Any attempt to do something, without completely buying into the Apple way of doing everything, leads to a torrent of cryptic undocumented errors. Even an old Unix guru like me can't keep up.

Reply