I've been doing development for Ubuntu Linux and remote debugging has
worked just fine, except for problems I've caused. When I see the
problem you describe, it's because the debugger stub does not have a
download directory set.
Charles Yeomans
On Jun 2, 2006, at 2:40 PM, Christian Miller wrote:
I dislike cross-posting, but have been unsuccessful in getting a
solution via the RB Forums. So, below, is the issue I'm having
trying to remote debug on Fedora Core 5 from the Mac OS X IDE:
Following up on my long Linux saga as of late... I've come full
circle and was able to get Fedora Core 5 on my network by disabling
ACPI.
I can SSH into the Linux box and VNC into the Linux box. However,
the remote debugger from the OS X IDE refuses to transfer the app
to the Linux stub.
While both were running (the IDE trying to transfer, and the stub
running). I nmapped from each machine to the other. The appropriate
ports were open while nmapping from Mac to Linux. However, the
corresponding ports were closed when checking from Linux to Mac.
One might automatically assume the Mac isn't accepting connections,
but I run no software firewall. And, connecting to the same
physical PC running Windows XP SP 2 has no problems communicating
with my Mac while remote debugging.
Additionally, the Mac IDE recognizes that it is connecting to
Linux. It makes the Linux build, starts the connection and then
things lock up. I have to click "stop" in the IDE, and force-close
the stub on Linux.
Ideas? Maybe I'll try the suggested MTU trick on this new install
later today.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
