• 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: Getting remote debugging to work
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Getting remote debugging to work


  • Subject: Re: Getting remote debugging to work
  • From: Matthew Formica <email@hidden>
  • Date: Tue, 05 Oct 2004 15:15:55 -0700

Nick,

As to your first question, remote debugging only works when both computers
are running Xcode 1.5.  It isn't designed to work when the remote computer
is running 10.2.8 with Project Builder.  This is why it fails.

On your second question, it looks like you are getting further, but your
path structures are different, which is stopping you.  The documentation
indicates that the remote executable and other files need to be at the same
path on both machines for remote debugging to work.  Have you tried setting
things up at the same path on both machines?

Finally, feel free to file an enhancement request asking for more
authentication mechanisms for remote debugging.

Regards,

--

Matthew Formica
Cocoa & Dev Tools Technology Evangelist
Apple Worldwide Developer Relations
email@hidden


On 10/4/04 11:41 AM, "email@hidden" <email@hidden> wrote:

> OK, so now I have access to a second test computer, and I'd like to set up
> remote debugging. So I turned it on, and followed some of the instructions on
> the ADC site, and I've been having some problems...
>
> 1. How do I get remote debugging to work if the Mac is running OS X 10.2.8?
> When I try to initiate the session, the remote debugger appears to attempt to
> access some resource that's in "Xcode.app" even though the December 2002
> developer tools predate Xcode.
>
> 2. How do I get remote debugging to work if the Mac is running OS X 10.3.5?
> The Mac has Xcode 1.5 installed, and it appears to go a little bit farther
> than #1 above, but it still stops and complains about "no executable present
> to run" after authentication. I tried to create a custom executable in the
> Xcode project that points to the executable's location on the remote computer,
> but then Xcode refused to allow me to debug the program even though the
> program was on a remote computer, probably because it was looking for the
> files on the local computer. Yes, the path structure on my computer and the
> remote computer is completely different, and I was hoping I would be able to
> work around this.
>
> 3. Why do I have to use public key authentication? Is there a way to get Xcode
> to use password authentication or should I file a bug report?
>
> I would appreciate answers to my questions. And yes, I did disable ZeroLink
> before trying any of this.
>
> Nick Zitzmann (using web mail)
> http://seiryu.home.comcast.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

References: 
 >Getting remote debugging to work (From: email@hidden)

  • Prev by Date: Re: man pages got nuked with Xcode 1.5
  • Next by Date: Re: Xcode 1.5 + svn = slow
  • Previous by thread: Getting remote debugging to work
  • Next by thread: How do I prevent XCode from parsing an email address?
  • Index(es):
    • Date
    • Thread