• 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: 32 vs. 64 bit confusion
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 32 vs. 64 bit confusion


  • Subject: Re: 32 vs. 64 bit confusion
  • From: Guillaume Billard <email@hidden>
  • Date: Thu, 26 Aug 2010 18:04:30 +0200

Hello,

I think I am in the situation described below, but I need to know what "easily enough" comes down to. :)

In our Xcode project, we used to have a i386 custom executable loading a i386 dylib file specified as an argument.
I just turned this custom executable into a universal binary containing both i386 and x86_64 versions of the app.
If I build and run the project with "i386" selected as the active architecture, the 32-bit version of the custom executable is ran, and the library loads fine.
But if I untick "Auto-attach debugger on crash" in the Debugging tab of the custom executable settings, the 64-bit version of the custom executable is used instead, and it can't load the library anymore.
The error message looks like this:
"dlopen(libX.dylib, 1): no suitable image found. Did find: libX.dylib: mach-o, but wrong architecture"
It seems it's because my OS is a 64-bit Snow Leopard, so the 64-bit version is picked by default.

So, when running the app from Xcode, what do I need to do for the 32-bit version of the custom executable to be used when the active architecture is i386 and the debugger is not attached on crash?
I tried using "arch" in the custom executable settings, but couldn't figure it out...
This is with Xcode 3.2.3.

Thanks!

Guillaume

Le 3 juin 2010 à 02:02, Alastair Houghton a écrit :

> On 2 Jun 2010, at 20:57, David Duncan wrote:
>
>>> 3) I am having trouble getting xcode to launch (say) Safari as either 32 or 64 bit to test both issues, can this be done?
>>
>> No idea, sorry =/.
>
> You can use the "arch" command line tool for this.  e.g.
>
>  arch -i386 /Applications/Safari.app/Contents/MacOS/Safari
>
> You should be able to trigger it from Xcode easily enough.
>
> Kind regards,
>
> Alastair.
>
> --
> http://alastairs-place.net
>
>
>
> _______________________________________________
> 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



 _______________________________________________
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

  • Prev by Date: Re: SDKROOT & MACOSX_DEPLOYMENT_TARGET
  • Next by Date: Re: A valid provisioning profile for this executable was not found.
  • Previous by thread: Symbol not always found in libstdc++ on 10.5
  • Next by thread: NS_FORMAT_FUNCTION broken on Xcode 3.2.3?
  • Index(es):
    • Date
    • Thread