8 Answers

• Detected an attempt to call a symbol in system libraries that is not present on the iPhone:
  mmap$UNIX2003 called from function _Z20TCMalloc_SystemAllocmPmm in image Shane McNeal.
  Detected an attempt to call a symbol in system libraries that is not present on the iPhone:
  pthread_cond_init$UNIX2003 called from function _ZN3WTI17TCMalloc_PageHeap4initEv in image Shane McNeal.
  Detected an attempt to call a symbol in system libraries that is not present on the iPhone:
  pthread_cond_wait$UNIX2003 called from function _ZN3WTI17TCMalloc_PageHeap15scavengerThreadEv in image Shane McNeal.
  Detected an attempt to call a symbol in system libraries that is not present on the iPhone:
  mprotect$UNIX2003 called from function _ZN2TI3JIT35privateCompileCTIMachineTrampolinesEPN3WTI6RefPtrINS_14ExecutablePoolEEEPNS_12TiGlobalDataEPNS_21MacroAssemblerCodePtrES9_S9_S9_ in image Shane McNeal.
  Detected an attempt to call a symbol in system libraries that is not present on the iPhone:
  munmap$UNIX2003 called from function _ZN2TI14ExecutablePool13systemReleaseERKNS0_10AllocationE in image Shane McNeal.
  

  Does that look like what you are getting? If so… We are alike, brotha.

• That is exactly what I am getting in my debug console. I know that this has been reported last week since the release of sdk 4.1; however, no solution till now.

• I have seen the issue ticket in appcelerator lighthouse. I hope they come up with something to resolve this.

• I have seen the issue ticket in appcelerator lighthouse. I hope they come up with something to resolve this.

• I have seen the issue ticket in appcelerator lighthouse. I hope they come up with something to resolve this.

• I see the same thing. It's been 2 months. Any ideas? thanks.

• In case anyone is still having these problems, this issue existed in 1.4.1, and 1.4.2 was released mainly to resolve it.
  Hence, the solution is to upgrade to 1.4.2.

• These were fixed with 1.4.2. Or rather, 1.4.2 exists to fix this issue.

  1.4.1 was an attempt to fix this, but the cure was worse than the problem as iOS 4.0.2 and later would kill the app when it tried to use the updated versions.

  1.4.1.1 is actually 1.4.0 with fixes in the build scripts to handle the then-new iTunes and SDK.

  1.4.2 is actually 1.4.0 with more build script fixes for the moving target that is iOS, and a new Titanium JS Core engine with Just in Time Compilation turned off. This means not even the updated symbols are used. The end result is that you don't get that warning and it still can run post 4.0.2.