I wanted to run a local debug session and followed the steps described in the LDT User Guide (embedded in Eclipse Help), but always get the "Process "..." takes too long to connect to IDE..." message.
Google gave me some hits, but as far as I see, all of them are related to v 0.9 and quite confusing: should debugging work in v1.0 straight away as described or do I need debugger.lua and debuginstrospection.lua and do I have to start a debug configuration AND run the application?
I'm trying to debug a simple hello world Lua application as described in the user guide. So the embedded interpreter should be used.
Here are the steps performed (according to the user guide v1.0):
- downloaded the 1.0 "Standalone product" (same problem occurs when installing LDT on a "fresh" Kepler version by using the marketplace)
- created a Lua project
- added a print("Hello world!") statement in main.lua
- set a breakpoint on the line containing the print() statement
- clicked "Debug as Lua application"
-> the "Process "..." takes too long to connect to IDE..." message pops up after the time out
-> Run as Lua application does work, i.e. the application starts and the "Hello world!" output appears as expected.
I had the debugger timing out with a new install of the LuaDevelopmentTools 1.0 and a break point on a print("Hello World" that I added to the main function. Following on from the comment of Firewall issues I noticed that my Firewall/Virus Check had an urgent update against my version of the JDK. By installing the latest JDK (JDK 7.21 Windows 64bit) everything started working. Not sure if it was Avast or the JDK but all works now.
Hope this helps others.