Hi,
The use of "external run config" is a kind of workaround because LDT don't support a "real" launch configuration. We will support that correctly in the 0.9.0 version (available at the end of the year).
Thijs Schreijer did a tutorial about the external run config with LDT. Did you try it ?
HTH

Hi,
Currently you use the debugger with external run configuration, but did you succeed to debug using command line ?

As you say the debugger don't search the good file.
To retrieve the absolute file path, we used the relative path returned by the lua debug API and the process working directory.
We did not found any reliable way to determine the current working dir for all platform.
Under linux we used the PWD Environment variable.
(we will not have this problem any more with the 0.9.0 version because working directory will be given by eclipse to the debugger)
Could you try to add this line

print (package.path)
print (os.getenv("PWD"))

at the begin of the file and give me the result to check if all is normal?
Simon

Hi Jason,
As better workaround than override os.getenv, you could define the environment variable in your external Tools configuration. you can use the "environment" tab to add the PWD variable. I never test it but that must work.
The 0.9.0 stable release should be released at the end of the year.
You could already test the last milestone release, and report us your feedback or any bugs about it .

The 0.9.0 stable release should be released at the end of the year.
You could already test the last milestone release, and report us your feedback or any bugs about it .

Thanks so much Simon, while also being super awesome, the new 0.9 milestone launching UI seems to fix this

Unfortunately however, I have a new problem with the debugger.

In the variables pane, where you can see all of the visible variables to a function, trying to display the
contents of a table breaks it. The entire pane becomes gray with this text printed: "Unable to load children
of <variable name>". This will persist with each step of the debugger until that variable is no longer visible
(such as stepping out of its function) or until the debug session ends.