• 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: Unable to debug custom executable
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

re: Unable to debug custom executable


  • Subject: re: Unable to debug custom executable
  • From: George Warner <email@hidden>
  • Date: Thu, 17 Apr 2008 14:24:14 -0700
  • Thread-topic: Unable to debug custom executable

On Thu, 17 Apr 2008 22:32:25 +0200, Dieter Oberkofler
<email@hidden> wrote:

> I'm trying to debug a Intel custom executable in XCode 2.5 but when
> using "Add custom executable" my application has an icon of a "invalid
> application" (icon is overlaid with some kind of a )crossed out circle
> and when trying to run the debugger all icons are grayed out. There
> are other applications that can be debugged using the same steps and
> the application has a "normal" icon in the Finder and can be executed
> without problems.
> I have been trying to see any differences to other applications but
> I'm stuck. Any help is appreciated. It would often be great to have
> XCode telling me why he "dislikes" what I want to do instead of just
> graying function out.

Chances are your project is setup to build a ppc executable (not a universal
binary or an Intel). The quickest way to test is to use the "file" command
in terminal to check the architecture of your applications executable file:

>From terminal cd to your applications "MacOS" folder and then type:

term> cd jucedemo.app/Contents/MacOS/
term> file jucedemo
jucedemo: Mach-O universal binary with 2 architectures
jucedemo (for architecture ppc):    Mach-O executable ppc
jucedemo (for architecture i386):    Mach-O executable i386

If it's not universal binary then it should be the same architecture as the
machine that you're running on.

In your target settings make sure that your debug configuration uses:

ARCHS = "$(NATIVE_ARCH)"

And in your release configuration you use:

ARCHS = ppc i386

--
Enjoy,
George Warner,
Schizophrenic Optimization Scientist
Apple Developer Technical Support (DTS)


 _______________________________________________
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

  • Follow-Ups:
    • Re: Unable to debug custom executable
      • From: Dieter Oberkofler <email@hidden>
  • Prev by Date: Re: Forcing Xcode to prefer a specific dylib
  • Next by Date: Re: Forcing Xcode to prefer a specific dylib
  • Previous by thread: Re: Unable to debug custom executable
  • Next by thread: Re: Unable to debug custom executable
  • Index(es):
    • Date
    • Thread