Lua Debug: Launch Process doesn't work since v2.0.0

[yosoymin]

In the latest version 2.0.0, the lua debugging doesn't work when you specify runtimeExecutable and runtimeArgs to the launch.json configuration. Attach Process configuration doesn't work either. However, the Launch Script configuration it's working properly.

[Bashakov]

I have the same problem, launching with and without debugging does not work. I don't use "runtimeExecutable" and "runtimeArgs". lua-debug.exe process actively uses the CPU. Process monitor, show that lua-debug.exe constantly opens and closes file C:\Users\user.vscode\extensions\actboy168.lua-debug-2.0.0-win32-x64\tmp\pid_xxxx

[actboy168]

I have the same problem, launching with and without debugging does not work. I don't use "runtimeExecutable" and "runtimeArgs". lua-debug.exe process actively uses the CPU. Process monitor, show that lua-debug.exe constantly opens and closes file C:\Users\user.vscode\extensions\actboy168.lua-debug-2.0.0-win32-x64\tmp\pid_xxxx

@Bashakov It doesn't look like the same problem. Can you provide a reproducible example?

[yosoymin]

It seems the version 2.0.1 solves the runtimeExecutable problem. Thanks!

[Bashakov]

@Bashakov It doesn't look like the same problem. Can you provide a reproducible example?

Steps to reproduce:

• Create new empty profile on vscode
• Add lua debug extension (now ver 2.0.1)
• Create new file "1.lua" with single line print"Hi"
• Edit launch.json { // Use IntelliSense to learn about possible attributes. // Hover to view descriptions of existing attributes. // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387 "version": "0.2.0", "configurations": [ { "type": "lua", "request": "launch", "name": "Debug", "program": "${workspaceFolder}/1.lua" } ] }
• Press F5 (start debugging)

Sometimes debug works as expected, i can step on code with F10, and program print "Hi" in terminal, full terminal output looks like:

PS C:\3>  & 'c:/Users/user/.vscode/extensions/actboy168.lua-debug-2.0.1-win32-x64/runtime/win32-x64/lua54/lua.exe' '-e' 'dofile[[c:/Users/user/.vscode/extensions/actboy168.lua-debug-2.0.1-win32-x64/script/launch.lua]];DBG[[6476-ansi]]' 'C:\3/1.lua'
Hi

but often vs code doesn't start debugging, scroll endless progress bar in "Debug and Run panel". And print in terminal only prepare command without program output:

PS C:\3>  c:; cd 'c:\3'; & 'c:/Users/user/.vscode/extensions/actboy168.lua-debug-2.0.1-win32-x64/runtime/win32-x64/lua54/lua.exe' '-e' 'dofile[[c:/Users/user/.vscode/extensions/actboy168.lua-debug-2.0.1-win32-x64/script/launch.lua]];DBG[[10480-ansi]]' 'C:\3/1.lua'

I use Processmon to capture success and fail run and discovered something interesting:

if successful I see:

• lua-debug.exe call CreateFile and CloseFile for file pid_6476 in loop
• lua.exe call CreateFile, QueryAttributeTagFile, SetDispositionInformationEx(Flags: FILE_DISPOSITION_DELETE, FILE_DISPOSITION_POSIX_SEMANTICS, FILE_DISPOSITION_FORCE_IMAGE_SECTION_CHECK), CloseFile. and made so twice.
• after lua.exe continue load (mgr.lua, event.lua, ... 1.lua)
• after what lua-debug.exe stop CreateFile/CloseFile loop

in case of failure:

• lua-debug.exe call CreateFile and CloseFile for file pid_4416 in loop
• lua.exe call CreateFile/QueryAttributeTagFile/SetDispositionInformationEx/CloseFile twice, but the third time CreateFile returns "NAME COLLISION" error.
• lua.exe write master.log and stay still run
• lua-debug.exe continue endless loop CreateFile/CloseFile

master.log contains messages like: [2023-10-11 09:29:10:039][[string " package.path = "c:/Users/user/.vsc..."]: 12][ERROR]ERROR:...y168.lua-debug-2.0.1-win32-x64/script/common\network.lua:77: bind: (Windows:10048)Обычно разрешается только одно использование адреса сокета (протокол/сетевой адрес/порт). stack traceback: [C]: in function 'assert' ...y168.lua-debug-2.0.1-win32-x64/script/common\network.lua:77: in function 'common.network'

    [C]: in function 'xpcall'
    [string "        package.path = "c:/Users/user/.vsc..."]:5: in main chunk
    [C]: in ?

[actboy168]

@Bashakov What is the Windows version number you are using?

[Bashakov]

Windows 10. Also i have instaled urbackup and Everything, which install own fs filters, may be it cause problem.

[actboy168]

More detailed version number. I mean 21H2 or 19044 like this.

[Bashakov]

Windows 10 Enterprise, 21H1, 19043.1083

[actboy168]

By default, lua-debug.exe uses unix domain socket to establish a connection with lua.exe. I don't know if there is some reason why your environment cannot use unix domain socket. You can try to use tcp instead. Add in launch.json:

"address": "127.0.0.1:<port>"

[Bashakov]

Looks like "address" fix the problem. All runs work as expected without problems, thx! Can I set this settings global, instead for each configurations in launch.json?