Debugging on windows - debugger cannot find path of lua script

Issue #127 resolved
oded fossfeld
created an issue

When trying to debug I get the following error:

"C:\Program Files\Lua\5.1\lua.exe" -e "package.path=[[C:/Users/yakir/.IdeaIC12/config/plugins/IDLua/remdebug/?.lua;]] .. package.path" -l remdebug tests/all_tests.lua Debugger connected at /127.0.0.1 C:\Program Files\Lua\5.1\lua.exe: cannot open tests/all_tests.lua: No such file or directory

This happens with every script I try to debug.

The same script with the same configuration can be run with no problems (without debugging) "C:\Program Files\Lua\5.1\lua.exe" tests/all_tests.lua".

Comments (14)

  1. Jon S Akhtar repo owner

    Yeah, don't run from program files. If you need it make a symlink.

    cd c:\
    mklink /j lua "C:\Program Files\Lua\5.1\"
    

    then your sdk needs to point to c:\lua\lua.exe

    you many need to monkey around a little.my lua is installed by lua for windows except I set the path at install to D:\Lua, so I have D:\Lua\5.1\lua.exe

  2. oded fossfeld reporter

    I did as you instructed - point the SDK to c:\lua\lua.exe however the problem persists. Pasting the executed line in the Shell seems to work. Perhaps this could be an issue with the working directory? Is there a way to get verbose logs from the plugin for more details?

  3. Jason P

    This seems to be a problem with the working directory.

    When launching the debug configuration, the working directory is ignored. However, when launching the normal run configuration, the working directory is obeyed.

    Using an absolute path for the script file will allow the debug configuration to actually launch but only if the working directory is not set at all. If the working directory is set to anything and the script file path is an absolute path, then it will fail to launch.

  4. Log in to comment