Description

rulatir

opened on Aug 11, 2019

Issue body actions

I can't start the "wait" debug configuration. It looks as if whatever listening process is launched by that configuration quits immediately and silently. The debug toolbar appears for a split second and then disappears. The small gray window with "devcat" icon that should say "Waiting for debuggee on 0.0.0.0:56789" (or something like that) does not appear at all.

This is happening on an Ubuntu machine at work:

$ uname -a
Linux rulatir-MS-7B24 4.18.0-20-generic #21-Ubuntu SMP Mon May 6 18:45:52 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

vscode details:

Version: 1.37.0
Commit: 036a6b1d3ac84e5ca96a17a44e63a87971f8fcc8
Date: 2019-08-08T01:24:14.598Z
Electron: 4.2.7
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Linux x64 4.18.0-20-generic

It works on my home box that runs Arch linux and probably vscode 1.36. I will fill the details once I'm back home.

Is there some way for me to debug this? Can I launch vscode without it detaching from the console so I can see what is being logged? Nothing relevant seems to appear in any log channels in the Output view, nothing on the devtools console either.

Activity

1. rulatir commented on Aug 11, 2019

   

   rulatir

   on Aug 11, 2019

   Author

   More actions

   Here is my 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": "attach",
               "name": "Wait for Lua debuggee",
               "workingDirectory": "/home/rulatir/projects/zuu",
               "listenPublicly": true,
               "listenPort": 56789
           }
       ]
   }
   

   I see nothing wrong with it, but there is a "Matches multiple schemas when only one must validate" warning about it, which is probably why it won't run:

   {
   	"resource": "/home/rulatir/projects/zuu/.vscode/launch.json",
   	"owner": "_generated_diagnostic_collection_name_#0",
   	"severity": 4,
   	"message": "Matches multiple schemas when only one must validate.",
   	"startLineNumber": 7,
   	"startColumn": 9,
   	"endLineNumber": 7,
   	"endColumn": 10
   }
   
2. rulatir commented on Aug 11, 2019

   

   rulatir

   on Aug 11, 2019

   Author

   More actions

   Sadly the above schema issue is probably irrelevant. I uininstalled the default vscode from the Ubuntu repositories and installed 1.36 snap. The schema issue is gone, but the launch configuration dying on me issue persists.

   Investigating potential problems with opening the port...
3. xaviergmail commented on Feb 11, 2021

   

   xaviergmail

   on Feb 11, 2021

   More actions

   After spending a while on this, I found out that the extension actually starts an .exe file. Since I was on WSL, I just had to reopen the folder with vscode running from Windows and it works fine!

Issue actions