You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 22, 2018. It is now read-only.
When selecting the debug deploy option in eclipse, the build appears to happen but the debugger fails to connect to the remote target.
https://www.chiefdelphi.com/forums/showthread.php?t=153511 lists out another user with the same symptoms. Although the debug-deploy ant target appears to build fine, the launching of the debugger drops into this loop and continues through all available attempts before giving up. RIO can be found over MDNS (that's what the deploy uses).
I am curious if the ant build call here is guaranteed to let the ant build finish before it returns. I haven't yet set up the environment to build/debug the plugin to find out.
We replicated this issue on two different PC's, and suspect it is present on a third...
For now, we are working around it by either using printf's, or manually starting the JVM on the RIO with the right debugger flags and manually setting eclipse to connect to the remote machine.
Tests were done with a fresh, new, unmodified IterativeRobot project
The text was updated successfully, but these errors were encountered:
Clarification: "debug-deploy ant target appears to build fine" means to say that when I ran the debug-deploy target in build.xml with a separate local installation of ant, it worked correctly. I noticed it does not appear that the return value "lastDeploy " is not checked before calling startDebugConfig() - if the ant build is failing for any reason, this could be problematic?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When selecting the debug deploy option in eclipse, the build appears to happen but the debugger fails to connect to the remote target.
https://www.chiefdelphi.com/forums/showthread.php?t=153511 lists out another user with the same symptoms. Although the debug-deploy ant target appears to build fine, the launching of the debugger drops into this loop and continues through all available attempts before giving up. RIO can be found over MDNS (that's what the deploy uses).
I am curious if the ant build call here is guaranteed to let the ant build finish before it returns. I haven't yet set up the environment to build/debug the plugin to find out.
We replicated this issue on two different PC's, and suspect it is present on a third...
For now, we are working around it by either using printf's, or manually starting the JVM on the RIO with the right debugger flags and manually setting eclipse to connect to the remote machine.
Tests were done with a fresh, new, unmodified IterativeRobot project
The text was updated successfully, but these errors were encountered: