Getting remote debugging to work
Getting remote debugging to work
- Subject: Getting remote debugging to work
- From: email@hidden
- Date: Mon, 04 Oct 2004 18:41:27 +0000
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