After vscode sets a breakpoint for the c++ file, the preLaunchTask is started successfully, but why did it not continue to debug, and how to troubleshoot what went wrong

[sunyd1006]

Environment

• OS and version: Linux j63g05242.sqa.eu95 4.19.91-011.ali4000.alios7.x86_64 Code completion with C/C++ extension #1 SMP Fri Jun 4 21:54:18 CST 2021 x86_64 x86_64 x86_64 GNU/Linux

• VS Code:
  Version: 1.97.2 (Universal)
  Commit: e54c774e0add60467559eb0d1e229c6452cf8447
  Date: 2025-02-12T23:20:35.343Z (1 mo ago)
  Electron: 32.2.7
  ElectronBuildId: 10982180
  Chromium: 128.0.6613.186
  Node.js: 20.18.1
  V8: 12.8.374.38-electron.0
  OS: Darwin x64 21.6.0

• C/C++ extension: 1.24.4

• OS and version of remote machine (if applicable): linux
  Linux j63g05242.sqa.eu95 4.19.91-011.ali4000.alios7.x86_64 Code completion with C/C++ extension #1 SMP Fri Jun 4 21:54:18 CST 2021 x86_64 x86_64 x86_64 GNU/Linux。

• GDB / LLDB version: 13.2

Bug Summary and Steps to Reproduce

Bug Summary:

After vscode sets a breakpoint for the c++ file, the preLaunchTask is started successfully, but why did it not continue to debug, and how to troubleshoot what went wrong

for you information:

• the main.out is compiled form x.cpp, and it has debuginfo , it useing g++ --std=c++11 -g x.cpp -o main.out
• i use gdb main.out, i can debug successfuly

my question：

• why can i not to debug in vscode , i successufly debug a sample demo in local(mac local) , but i cannot debug in remote server.
• How to debug the error of this debug server
• there are soo many tab in red box, which one can i to find log to debug?

Debugger Configurations

"version": "0.2.0",
    "configurations": [
        {
            "name": "(gdb) Launch my",
            "type": "cppdbg",
            "request": "launch",
            "program": "/apsara/sunyindong.syd/codespace/odps_src/main.out",
            "args": [],
            "stopAtEntry": false,
            "cwd": "${workspaceFolder}",
            "environment": [],
            "externalConsole": false,
            "linux": {
                "MIMode": "gdb"
            },
            "osx": {
                "MIMode": "lldb"
            },
            "miDebuggerPath": "/apsara/sunyindong.syd/env_install/gdb-13.2/gdb/gdb"
            // "setupCommands": [
            //     {
            //         "description": "Enable pretty-printing for gdb",
            //         "text": "-enable-pretty-printing",
            //         "ignoreFailures": true
            //     },
            //     {
            //         "description": "Set Disassembly Flavor to Intel",
            //         "text": "-gdb-set disassembly-flavor intel",
            //         "ignoreFailures": true
            //     }
            // ]
        }
   ]
}

Debugger Logs

no debug consolde or output windows infomation. because there are bath nothing.

Other Extensions

No response

Additional Information

No response

[sean-mcmanus]

@sunyd1006 Does it work with an earlier version, such as 1.22.11 or 1.23.6? i.e. are you hitting #13219 ?

[sunyd1006]

thanks you very much, you are my god~