coder / code-server

VS Code in the browser
https://coder.com
MIT License
67.71k stars 5.55k forks source link

Debugger does not start on C++, C#, Python, Go, PHP code #4221

Closed globalww closed 2 years ago

globalww commented 2 years ago

OS/Web Information

Steps to Reproduce

  1. Write a CPP code and press debug

    Expected

Debugger should start

Actual

Opens launch.json and nothing happens. Deleting launch.json temporarily solves the problem but after recreating launch.json, same problem happens again.

Screenshot

2

Notes

After updating 3.12.0 this problem started to happen. It worked fine before. I tried deleting all JSON configuration files and creating it again, reinstalling C/C++ plugin, and selecting other debug options, but nothing worked for me.

I'm not familiar with VSCode so maybe it is my configuration problem, and sorry if it is.

jsjoeio commented 2 years ago

Hmm...I'm wondering if this is a duplicate of any of these:

I am not familiar with C++. If you can update the repro steps with step-by-step instructions (assume no C++ experience), then I can try locally and look into this.

senyai commented 2 years ago

Similar issue here. I have a c++ configuration in launch.json and debugging worked before. It looks like vscode tries to debug file that is currently edited (makes no sense). When launch.json is opened and I try to start c++ debugging by selecting my configuration, I see this message: image

jsjoeio commented 2 years ago

Hmm...well if you can post repro steps, I can take a look! @senyai

senyai commented 2 years ago

Let's try

0) install gcc and cmake; 1) Install code-server like this:

wget https://code-server.dev/install.sh && \
    sh install.sh --version 3.12.0 --method=standalone && \
    rm install.sh &&
wget https://github.com/microsoft/vscode-cpptools/releases/download/1.6.0/cpptools-linux.vsix && \
    /home/devel/.local/bin/code-server --install-extension cpptools-linux.vsix && \
    /home/devel/.local/bin/code-server --install-extension twxs.cmake && \
    /home/devel/.local/bin/code-server --install-extension ms-vscode.cmake-tools && \
    /home/devel/.local/bin/code-server --install-extension ms-python.python && \
    /home/devel/.local/bin/code-server --install-extension mhutchie.git-graph && \
    /home/devel/.local/bin/code-server --install-extension christian-kohler.path-intellisense

2) Create directory with 2 files: CMakeLists.txt:

cmake_minimum_required(VERSION 3.10)
project(code_server_issues_4221)
set(CMAKE_CXX_STANDARD 17)
add_executable(code_server_issues_4221 code_server_issues_4221.cpp)

and code_server_issues_4221.cpp:

#include <iostream>

int main(int argc, char** argv) {
    if (argc == 2) {
        std::cout << "jsjoeio happy\n";
    } else {
        std::cout << "senyai sad\n";
    }
    return 0;
}

3) Press F1 -> "CMake: Configure" 4) Press F5, launch.json will be created 5) Press F5, debugging will not start

senyai commented 2 years ago

Very similar issue https://github.com/microsoft/vscode/issues/133178

PabloZaiden commented 2 years ago

It's not related to C++. I'm having the exact same issue with C#.

And, indeed, this is the commit that fixed it in codespaces: https://github.com/microsoft/vscode/commit/63504d9cfa211e8e09660964d6b0d8280d6f9d12

It doesn't seem that has been applied here yet.

cleardusk commented 2 years ago

The same problem as @globalww @PabloZaiden, when debugging python. Will it be fixed in the next release?

jsjoeio commented 2 years ago

@senyai thank you for the repro steps!

Video

Here is a video of me going through those steps: https://youtu.be/-9y8GLocrqw (still uploading & processing atm)

When launch.json is opened and I try to start c++ debugging by selecting my configuration, I see this message:

Same thing happened to me.

jsjoeio commented 2 years ago

And, indeed, this is the commit that fixed it in codespaces: microsoft/vscode@63504d9

Thanks for linking to the commit! If fixing this means adding that commit to our fork of VS Code then we should be able to make that happen in our current sprint. Adding it to the version milestone.

jsjoeio commented 2 years ago

cc @TeffenEllis just giving you a heads-up on this!

cleardusk commented 2 years ago

@jsjoeio Debugger does not start on Python, too.

GirlBossRush commented 2 years ago

@jsjoeio @cleardusk @globalww,

I believe this may be resolved in upstream’s version 1.60.2, which we’re targeting in next week’s release schedule. Thank you for your patience!

frank8922 commented 2 years ago

I noticed whenever I right click in my c++ file and select "build and debug active file" it works, it also seems to work once after refreshing the page but when I immediately try and start the debugger it fails again, only after each refresh does it work one time again. Hope this contributes something at least

https://user-images.githubusercontent.com/32795234/135478074-49d98a2c-318a-433d-9842-2b0e4c65ab27.MP4

steeeffen commented 2 years ago

Same behavior for java debugging as well, at least any entry of type "attach" in launch.json is ignored and debugger wants to use the current open file.

coverthesea commented 2 years ago

Same behavior for golang debugging as well

Gandalf1783 commented 2 years ago

For me, the debugging works on the first time i reload the window. After that, i cant start the debugger. It then asks me to select an environment and then like discussed here just opens the launch.json file. It even executes my Build-Task from tasks.json correctly, and then debugs it properly with breakpoints etc. The project is written in C.

Just saw that frank8922 wrote that too. Exactly the same behaviour for me.

bonarealm commented 2 years ago

can not debug php also.

marius-lupu commented 2 years ago

Doesn't work also for me for a Python or a Go app. The solution is to use 3.11.0

lishunan246 commented 2 years ago

Any updates?

Was it fixed in v4.1.0?

jsjoeio commented 2 years ago

@lishunan246 I haven't checked but you're welcome to and then let us know!

lishunan246 commented 2 years ago

@lishunan246 I haven't checked but you're welcome to and then let us know!

I confirm that the debugger works in v4.1.0.

bonarealm commented 2 years ago

Yes,it works.thanks for your attention and hard works.

jsjoeio commented 2 years ago

Thank you @lishunan246 and @bonarealm ♥️