• 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 my app on machine it wasn't built on
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Unable to debug my app on machine it wasn't built on


  • Subject: Re: Unable to debug my app on machine it wasn't built on
  • From: Jens Alfke <email@hidden>
  • Date: Tue, 27 May 2008 16:20:00 -0700


On 27 May '08, at 1:22 PM, Greg Guerin wrote:

I don't know why a 10.5.2 host would consider these "unknown".
A 10.4 host would make more sense, as these are not defined there.

Aha! The problem turned out to be obsolete developer tools — I checked the version numbers of gdb on both machines, and the Mini still had 6.1 (from Tiger). I think what happened was that, last year when I upgraded the Mini to Leopard, I skipped Xcode due to lack of disk space, since I wasn't using that machine for anything work related. So the developer tools, including command-line stuff, all remained at 10.4. I'm upgrading now. Thanks for the hint!


—Jens

Attachment: smime.p7s
Description: S/MIME cryptographic signature

 _______________________________________________
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: 
 >Re: Unable to debug my app on machine it wasn't built on (From: Greg Guerin <email@hidden>)

  • Prev by Date: Re: CrashReporter prevents my debugged application from going away
  • Next by Date: Re: I'm new to Xcode, and . . .
  • Previous by thread: Re: Unable to debug my app on machine it wasn't built on
  • Next by thread: Python-Cocoa include external modules?
  • Index(es):
    • Date
    • Thread