• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Xcode 2.5 can't #include_next <stdarg.h>
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Xcode 2.5 can't #include_next <stdarg.h>


  • Subject: Re: Xcode 2.5 can't #include_next <stdarg.h>
  • From: Steve Mills <email@hidden>
  • Date: Thu, 1 Nov 2007 16:14:12 -0500

On Nov 1, 2007, at 12:26:10, Steve Mills wrote:

Everything now builds since changing to $(DEVELOPER_SDK_DIR) in those places. The only new warnings are these:

Checking Dependencies
Building target “Creator Pro” of project “Creator” with configuration “Debug”


warning: skipping file '$(SYSTEM_DEVELOPER_DIR)/SDKs/MacOSX10.4u.sdk/ usr/lib/libz.1.dylib' (unexpected file type 'compiled.mach-o' in Frameworks & Libraries build phase)
warning: skipping file '$(SYSTEM_DEVELOPER_DIR)/SDKs/MacOSX10.4u.sdk/ usr/lib/libcrypto.0.9.7.dylib' (unexpected file type 'compiled.mach- o' in Frameworks & Libraries build phase)
warning: skipping file '$(SYSTEM_DEVELOPER_DIR)/SDKs/MacOSX10.4u.sdk/ usr/lib/libssl.0.9.7.dylib' (unexpected file type 'compiled.mach-o' in Frameworks & Libraries build phase)


If I ignore those warnings and let it run with the debugger, it stops an EXC_BAD_ACCESS followed by:

mi_cmd_stack_list_frames: Not enough frames in stack.
mi_cmd_stack_list_frames: Not enough frames in stack.

The stack looks like it's trying to init a static global C++ object, which is a custom override of string<uchar>, which is being converted from some constant ASCII text by our own conversion routine, which calls TECConvertText and friends. I'm guessing that thread of the code is a red herring, and the actual problem is based on those 3 warnings above. The same project runs fine in 2.4.1 on 10.4.10.

BTW, I wanted to give a big thanks to everyone at Apple, especially the Xcode team, for all the help you've been since the 10.5 release. Just when you think you can relax after a product ships, then you have to start supporting it. The cycle never ends. :)

Steve Mills
Drummer, Mac geek
http://sjmills5.home.mchsi.com/


_______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
References: 
 >Xcode 2.5 can't #include_next <stdarg.h> (From: Steve Mills <email@hidden>)
 >Re: Xcode 2.5 can't #include_next <stdarg.h> (From: Chris Espinosa <email@hidden>)
 >Re: Xcode 2.5 can't #include_next <stdarg.h> (From: Steve Mills <email@hidden>)
 >Re: Xcode 2.5 can't #include_next <stdarg.h> (From: Steve Mills <email@hidden>)
 >Re: Xcode 2.5 can't #include_next <stdarg.h> (From: Rick Ballard <email@hidden>)
 >Re: Xcode 2.5 can't #include_next <stdarg.h> (From: Steve Mills <email@hidden>)
 >Re: Xcode 2.5 can't #include_next <stdarg.h> (From: Steve Mills <email@hidden>)

  • Prev by Date: Re: #if for current SDK...?
  • Next by Date: Interface Builder can't read class file
  • Previous by thread: Re: Xcode 2.5 can't #include_next <stdarg.h>
  • Next by thread: Re: Xcode 2.5 can't #include_next <stdarg.h>
  • Index(es):
    • Date
    • Thread