Issues with SDK 4.1(!?) « cocos2d for iPhone

cocos2d for iPhone » Programming » cocos2d support (graphics engine)

Issues with SDK 4.1(!?)

(11 posts) (9 voices)

Started 1 year ago by Arjan
Latest reply from arcticfire

Tags:

iOS 4.1
SDK

Arjan
Member
Hey guys!
First of all, kudos to riq and all the excellent contributors. I'm developing with cocos2d for about a month now and it works like a charm. Thanks a lot!
After switching to the iOS SDK 4.1 last night i begin to encounter a few problems which are likely to be connected to said upgrade. After switching the base SDK MY project itselfs runs without problems except for the simulator debug which keeps outputting lines like
```
Detected an attempt to call a symbol in system libraries that is not present on the iPhone:
open$UNIX2003 called from function _ZN4llvm12MemoryBuffer7getFileEPKcPSsx in image libLLVMContainer.dylib.
Detected an attempt to call a symbol in system libraries that is not present on the iPhone:
fstat$INODE64 called from function _ZN4llvm12MemoryBuffer7getFileEPKcPSsx in image libLLVMContainer.dylib.
Detected an attempt to call a symbol in system libraries that is not present on the iPhone:
mmap$UNIX2003 called from function _ZN4llvm3sys4Path14MapInFilePagesEiy in image libLLVMContainer.dylib.
Detected an attempt to call a symbol in system libraries that is not present on the iPhone:
close$UNIX2003 called from function _ZN4llvm12MemoryBuffer7getFileEPKcPSsx in image libLLVMContainer.dylib.
```
multiple times DIRECTLY AFTER the app boots, even before the cocos2d startup debug info shows. The app itself runs fine, though.
The issue isn't present on the iPhone at all. Is this only some unimportant stuff that'll disappear in the next releases of cocos, or am i missing something here?
All the cocos2d demos an tests won't even compile anymore, i only get hundreds of errors. I guess i am missing something simple here? (base sdk is right of course).
I searched the forum and the interwebs, but (especially concerning problem 1) I literally found almost nothing.

Thanks in advance and I hope some of you guys have a clue what's going on.
Posted 1 year ago #
riq
Key Master

did you also change the BASE SDK to 4.1 for the Debug-Simulator configuration ?

Posted 1 year ago #

Arjan
Member

Okay, forget about the demo project 4.1 problem. still doesn't work (checked debug-sim config again) I think it just needs a fresh start.
I created a new project from the standard cocos Hello World template, changed the SDKs accordingly, everything's fine. BUT: the problem with the debugger messages quoted in my first post still occur (ONLY on the simulator, NOT on the device). I guess this could be a (new) cocos2d issue?! Note that the app runs without problems, nevertheless.
Do you, riq, or someone else also noticed this issue? Otherwise just file it as a bug report ;)

Log from fresh (working) cocos2d template:

[Session started at 2010-09-09 23:26:29 +0200.]
2010-09-09 23:26:50.605 sdk 41 test[5204:207] cocos2d: cocos2d v0.99.4
2010-09-09 23:26:50.762 sdk 41 test[5204:207] cocos2d: Using Director Type:CCDisplayLinkDirector
2010-09-09 23:26:51.131 sdk 41 test[5204:207] cocos2d: GL_VENDOR:   Apple Computer, Inc.
2010-09-09 23:26:51.133 sdk 41 test[5204:207] cocos2d: GL_RENDERER: Apple Software Renderer
2010-09-09 23:26:51.133 sdk 41 test[5204:207] cocos2d: GL_VERSION:  OpenGL ES-CM 1.1 APPLE
2010-09-09 23:26:51.135 sdk 41 test[5204:207] cocos2d: GL_MAX_TEXTURE_SIZE: 2048
2010-09-09 23:26:51.135 sdk 41 test[5204:207] cocos2d: GL_MAX_MODELVIEW_STACK_DEPTH: 16
2010-09-09 23:26:51.136 sdk 41 test[5204:207] cocos2d: GL supports PVRTC: YES
2010-09-09 23:26:51.137 sdk 41 test[5204:207] cocos2d: GL supports BGRA8888 textures: NO
2010-09-09 23:26:51.137 sdk 41 test[5204:207] cocos2d: GL supports NPOT textures: YES
2010-09-09 23:26:51.138 sdk 41 test[5204:207] cocos2d: GL supports discard_framebuffer: YES
2010-09-09 23:26:51.138 sdk 41 test[5204:207] cocos2d: compiled with NPOT support: NO
2010-09-09 23:26:51.139 sdk 41 test[5204:207] cocos2d: compiled with VBO support in TextureAtlas : YES
2010-09-09 23:26:51.140 sdk 41 test[5204:207] cocos2d: compiled with Affine Matrix transformation in CCNode : YES
2010-09-09 23:26:51.140 sdk 41 test[5204:207] cocos2d: compiled with Profiling Support: NO
2010-09-09 23:26:51.940 sdk 41 test[5204:207] cocos2d: Frame interval: 1
2010-09-09 23:26:51.942 sdk 41 test[5204:207] cocos2d: surface size: 320x480
Detected an attempt to call a symbol in system libraries that is not present on the iPhone:
open$UNIX2003 called from function _ZN4llvm12MemoryBuffer7getFileEPKcPSsx in image libLLVMContainer.dylib.
Detected an attempt to call a symbol in system libraries that is not present on the iPhone:
fstat$INODE64 called from function _ZN4llvm12MemoryBuffer7getFileEPKcPSsx in image libLLVMContainer.dylib.
Detected an attempt to call a symbol in system libraries that is not present on the iPhone:
mmap$UNIX2003 called from function _ZN4llvm3sys4Path14MapInFilePagesEiy in image libLLVMContainer.dylib.
Detected an attempt to call a symbol in system libraries that is not present on the iPhone:
close$UNIX2003 called from function _ZN4llvm12MemoryBuffer7getFileEPKcPSsx in image libLLVMContainer.dylib.
Detected an attempt to call a symbol in system libraries that is not present on the iPhone:
pthread_mutexattr_destroy$UNIX2003 called from function _ZN4llvm3sys5MutexC2Eb in image libLLVMContainer.dylib.

Posted 1 year ago #

JonKean
Member

just ignore the warnings, it's only the simulator.

Posted 1 year ago #
Arjan
Member

That's what I keep saying to myself...
Okay, did a few further tests. Seems to be SOME open gl es problem. The outputs only occur in open gl es apps, even from the apple templates. cocoa touch is fine, though. I guess it's not a cocos problem.
Would be interesting if someone else also encounters these problems...

Anyways, thanks a lot for your feedback!!!

Posted 1 year ago #
Zzoony
Member

In my case, That occurred didn't work CCFadeTRTransition.
Maybe some OpenGL ES function changed. I think.

Posted 1 year ago #
Adam Allen
Member

I too got these notices after upgrading to iOS 4.1 and cocos2d v0.99.5-beta2. They only appear in the simulator and not on my device; however my device is running 3.1.3.

Posted 1 year ago #
CJ
Moderator

Confirmed only in simulator with Apple's GL template project as well.

Posted 1 year ago #
liquidfire
Member

Hmm, this is even happening to my non-Cocos2D OpenGL | ES apps on the simulator.

Any solutions yet / Are they harmless?

Posted 1 year ago #
Vanny
Member
Any updates on this? I upgraded to the latest SDK, and set the base SDK to 4.1 and targeted 3.0 and I get this error as well as:
```
<Error>: CGContextSetGrayFillColor: invalid context 0x0
<Error>: CGContextTranslateCTM: invalid context 0x0
<Error>: CGContextScaleCTM: invalid context 0x0
```
The app runs fine as far as I can tell, I never had these issues before upgrading. I get it with 0.99.4 and 0.99.5
Posted 1 year ago #

arcticfire
Member

i also get them.

[Session started at 2010-12-01 20:55:27 -0800.]
Detected an attempt to call a symbol in system libraries that is not present on the iPhone:
open$UNIX2003 called from function _ZN4llvm12MemoryBuffer7getFileEPKcPSsx in image libLLVMContainer.dylib.
Detected an attempt to call a symbol in system libraries that is not present on the iPhone:
fstat$INODE64 called from function _ZN4llvm12MemoryBuffer7getFileEPKcPSsx in image libLLVMContainer.dylib.
Detected an attempt to call a symbol in system libraries that is not present on the iPhone:
mmap$UNIX2003 called from function _ZN4llvm3sys4Path14MapInFilePagesEiy in image libLLVMContainer.dylib.
Detected an attempt to call a symbol in system libraries that is not present on the iPhone:
close$UNIX2003 called from function _ZN4llvm12MemoryBuffer7getFileEPKcPSsx in image libLLVMContainer.dylib.
iSimulate: You are running SDK version 20100429 with OpenGL support
Detected an attempt to call a symbol in system libraries that is not present on the iPhone:
pthread_mutexattr_destroy$UNIX2003 called from function _ZN4llvm3sys5MutexC2Eb in image libLLVMContainer.dylib.

But i need to use iSimulate, and it doesn't send touches or accelerometer data at all....

Posted 1 year ago #

RSS feed for this topic

Reply

You must log in to post.