2025-12-25T20:14:49Z

I am having hard time while trying to debug a Node.JS app with the visual interface of VS Code. Firebase studio has only the option to "Install additional debuggers..." The option to "Install additional debuggers..." typically appears when the necessary debugger component for a specific project type (e.g. JavaScript, C#, Python, C++) is not installed or configured correctly in a IDE, such as Visual Studio Code (VS Code) or potentially an integrated Firebase Studio environment

Can anybody help me debug this Node.JS project?

2025-12-24T14:30:47Z

I am trying to figure it out why while debugging in Visual Studio Code the first template Flutter app the debugger is not catching the instruction:

_counter++;

_counter--;

Here, I am attaching the debugging process, I am expecting the debugger to hold breakpoint on every line that I have selected breakpoint. The breakpoint only activates on line 64. It does not activates on line 63 and 65, why is that?

The issue only occurs when running program in Google Chrome (web app). It does not occur when running on android emulator. In addition, the same program in Android Studio while debugging the debugger holds on line 62, 63, 64 and 65 while running in Google Chrome

2021-01-06T15:45:56Z

I installed VSC and wrote this program

#include <stdio.h>

int main( void )
{
    printf("Hello world!");
}

Then I installed a C/C++ debugger and I saved the file on the desktop as "hello.c" and magically the syntax became higlighted.

Now I would like to run the program, but can't find a way.
There's no "run" or "build" option anywhere, and if I start the debugging and choose the debugger then I got a new tab named "settings.json" with a couple of brackets waiting for me to write something.

Also in the left I can read that I "have not yet opened a folder". What does it even mean?

And the line #include <stdio.h> is underlined in red, like there's something wrong going on, maybe I have to download the library?

I would do anything to see the output of the program, please help me.

2023-06-15T18:07:22Z

I have hardware available through my university jump host, to which I connect to through ssh:

$ ssh username@login.university.edu
Password: *******

$ ssh hardware1
Password: *******

[my_computer] --> [login.university.edu] --> [hardware1]

I can get a window to login.university.edu with VSCode Remote SSH Connect to Host, but then once there I use the terminal to SSH into hardware1, therefore I can't use the debugger on hardware1.

How could I get a window to hardware1? Or else how can I customize launch.json in order to run ssh hardware1 and input my password?

2025-10-12T10:14:23Z

I use Python 3.11.1 and Jupyter Notebook to run code selections or lines in the Interactive Window for debugging or coding purposes.

A few days ago, everything was working fine, and I didn't have any issues running my code. However, after being away for two days, when I opened my project again and tried to run my code starting with importing pandas in the Interactive Window, it kept getting stuck at "Connecting to kernel".

I’ve already performed a clean uninstall and reinstalled Visual Studio Code, Jupyter, and Python, but the issue remains the same. Could this problem be caused by the September 2025 Visual Studio Code update (version 1.105), released on October 9th, 2025?

2025-12-14T14:21:52Z

I am getting the following error (debugger output) when i try to do "ST_LINK: attach to application" in vscode. I have no idea what is going on. Any help is greatly appreciated.

I use WSL ubuntu 22.04.

My version of vscode is1.107.0 (user setup).

Cortex-Debug: VSCode debugger extension version 1.12.1 git(652d042). Usage info: https://github.com/Marus/cortex-debug#usage
"configuration": {
    "name": "ST-Link: Attach to Application",
    "cwd": "/home/federico/bare-metal-series/app",
    "executable": "/home/federico/bare-metal-series/app/firmware.elf",
    "servertype": "stutil",
    "request": "attach",
    "type": "cortex-debug",
    "device": "STM32F401RE",
    "runToEntryPoint": "main",
    "interface": "swd",
    "showDevDebugOutput": "raw",
    "armToolchainPath": "/opt/gcc-arm-none-eabi/bin",
    "__configurationTarget": 6,
    "gdbServerConsolePort": 55878,
    "pvtAvoidPorts": [],
    "chainedConfigurations": {
        "enabled": false
    },
    "debuggerArgs": [],
    "swoConfig": {
        "enabled": false,
        "decoders": [],
        "cpuFrequency": 0,
        "swoFrequency": 0,
        "source": "probe"
    },
    "rttConfig": {
        "enabled": false,
        "decoders": []
    },
    "graphConfig": [],
    "preLaunchCommands": [],
    "postLaunchCommands": [],
    "preAttachCommands": [],
    "postAttachCommands": [],
    "preRestartCommands": [],
    "postRestartCommands": [],
    "preResetCommands": [],
    "postResetCommands": [],
    "toolchainPath": "/opt/gcc-arm-none-eabi/bin",
    "toolchainPrefix": "arm-none-eabi",
    "extensionPath": "/home/federico/.vscode-server/extensions/marus25.cortex-debug-1.12.1",
    "registerUseNaturalFormat": true,
    "variableUseNaturalFormat": true,
    "pvtVersion": "1.12.1",
    "__sessionId": "1b5c4f93-51d1-4784-b53d-5821e9169153",
    "pvtShowDevDebugOutput": "raw"
}
Reading symbols from /opt/gcc-arm-none-eabi/bin/arm-none-eabi-objdump --syms -C -h -w /home/federico/bare-metal-series/app/firmware.elf
Reading symbols from /opt/gcc-arm-none-eabi/bin/arm-none-eabi-nm --defined-only -S -l -C -p /home/federico/bare-metal-series/app/firmware.elf
Launching GDB: /opt/gcc-arm-none-eabi/bin/arm-none-eabi-gdb -q --interpreter=mi2
1-gdb-version
Launching gdb-server: st-util -p 50000 --no-reset
    Please check TERMINAL tab (gdb-server) for output from st-util
Finished reading symbols from objdump: Time: 37 ms
Finished reading symbols from nm: Time: 52 ms
-> =thread-group-added,id="i1"
-> ~"GNU gdb (Arm GNU Toolchain 14.3.Rel1 (Build arm-14.174)) 15.2.90.20241229-git\n"
-> ~"Copyright (C) 2024 Free Software Foundation, Inc.\n"
-> ~"License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>\nThis is free software: you are free to change and redistribute it.\nThere is NO WARRANTY, to the extent permitted by law."
-> ~"\nType \"show copying\" and \"show warranty\" for details.\n"
-> ~"This GDB was configured as \"--host=x86_64-pc-linux-gnu --target=arm-none-eabi\".\n"
-> ~"Type \"show configuration\" for configuration details.\n"
-> ~"For bug reporting instructions, please see:\n"
-> ~"<https://bugs.linaro.org/>.\n"
-> ~"Find the GDB manual and other documentation resources online at:\n    <"
-> ~"http://www.gnu.org/software/gdb/documentation/>.\n\n"
-> ~"For help, type \"help\".\n"
-> ~"Type \"apropos word\" to search for commands related to \"word\".\n"
-> 1^done
2-gdb-set mi-async on
-> 2^done
3-interpreter-exec console "set print demangle on"
-> 3^done
4-interpreter-exec console "set print asm-demangle on"
-> =cmd-param-changed,param="print asm-demangle",value="on"
-> 4^done
5-enable-pretty-printing
-> 5^done
6-interpreter-exec console "source /home/federico/.vscode-server/extensions/marus25.cortex-debug-1.12.1/support/gdbsupport.init"
-> 6^done
7-interpreter-exec console "source /home/federico/.vscode-server/extensions/marus25.cortex-debug-1.12.1/support/gdb-swo.init"
-> =cmd-param-changed,param="language",value="c"
-> =cmd-param-changed,param="language",value="auto"
-> 7^done
8-interpreter-exec console "set output-radix 0xa"
-> ~"Output radix now set to decimal 10, hex a, octal 12.\n"
Output radix now set to decimal 10, hex a, octal 12.
-> 8^done
9-interpreter-exec console "set input-radix 0xa"
-> ~"Input radix now set to decimal 10, hex a, octal 12.\n"
Input radix now set to decimal 10, hex a, octal 12.
-> 9^done
10-file-exec-and-symbols "/home/federico/bare-metal-series/app/firmware.elf"
-> 10^done
11-target-select extended-remote localhost:50000
-> =thread-group-started,id="i1",pid="42000"
-> =thread-created,id="1",group-id="i1"
-> ~"0x08000ac2 in ?? ()\n"
0x08000ac2 in ?? ()
-> *stopped,frame={addr="0x08000ac2",func="??",args=[],arch="armv7e-m"},thread-id="1",stopped-threads="all"
mi2.status = stopped
Program stopped, probably due to a reset and/or halt issued by debugger
-> 11^connected
12-interpreter-exec console "monitor halt"
-> 12^done
13-thread-list-ids
-> 13^done,thread-ids={thread-id="1"},current-thread-id="1",number-of-threads="1"
14-thread-info 1
-> 14^done,threads=[{id="1",target-id="Thread <main>",frame={level="0",addr="0x08000ac2",func="??",args=[],arch="armv7e-m"},state="stopped"}]
15-stack-list-frames --thread 1 0 19
-> 15^done,stack=[frame={level="0",addr="0x08000ac2",func="??",arch="armv7e-m"},frame={level="1",addr="0x08000abe",func="??",arch="armv7e-m"}]
16-stack-list-frames --thread 1 0 19
-> 16^done,stack=[frame={level="0",addr="0x08000ac2",func="??",arch="armv7e-m"},frame={level="1",addr="0x08000abe",func="??",arch="armv7e-m"}]

The code im trying to run is this one. It is about having a LED blink.

#include <libopencm3/stm32/rcc.h>
#include <libopencm3/stm32/gpio.h>
#define LED_PORT (GPIOA)
#define LED_PIN (GPIO5)

static void rcc_setup(void) {
rcc_clock_setup_pll(&rcc_hsi_configs[RCC_CLOCK_3V3_84MHZ]);
}

static void gpio_setup(void) {
  rcc_periph_clock_enable(RCC_GPIOA);
gpio_mode_setup(LED_PORT, GPIO_MODE_OUTPUT, GPIO_PUPD_NONE, LED_PIN);
}

static void delay_cycles(uint32_t cycles){
  for(uint32_t i=0; i<cycles; i++){
    __asm__("nop");
  }
}


int main(void) {
rcc_setup();
gpio_setup();

  while (1) {
    gpio_toggle(LED_PORT, LED_PIN);
    delay_cycles(84000000/4);
  
  }

  // Never return
  return 0;
}

Launch.json file is the following:

{
  "configurations": [
    {
      "name": "ST-Link: Debug Application",
      "cwd": "${workspaceFolder}/app",
      "executable": "./firmware.elf",
      "servertype": "stutil",
      "request": "launch",
      "type": "cortex-debug",
      "device": "STM32F401RE",
      "runToEntryPoint": "main",
      "showDevDebugOutput": "raw",
      "interface": "swd",
      "preLaunchTask": "build_debug",
      "armToolchainPath": "/opt/gcc-arm-none-eabi/bin"
    },
    {
      "name": "ST-Link: Attach to Application",
      "cwd": "${workspaceFolder}/app",
      "executable": "./firmware.elf",
      "servertype": "stutil",           
      "request": "attach",
      "type": "cortex-debug",
      "device": "STM32F401RE",
      "runToEntryPoint": "main",
      "interface": "swd",
      "showDevDebugOutput": "raw",
      "armToolchainPath": "/opt/gcc-arm-none-eabi/bin"
    }
  ]
}

When i type st-util the board is recognized. Vscode recognizes the board.

Not sure what else to say. The toolchain seems right to me.

The file structure of my project is:

bare-metal-series:
    app:
        src:
            firmware.c
        

        firmware.elf
        firmware.map
        firmware.bin

    .vscode:
        launch.json

    libopencm3:
        include:
            libopencm3:
                stm32:
                    rcc.h
                    gpio.h

2025-03-20T16:22:10Z

I have the "Run and Debug" tab in the bottom panel, together with other tabs like "Terminal" and "Test results". When I debug a test from the test explorer, "Test results" pops open. If a breakpoint is hit, the relevant file opens in the editor, but "Test results" remains open doing nothing.

How do I get it to focus "Run and Debug" on break, so I can actually act on what's happening?

2025-10-27T02:43:57Z

I have my Expo project running on port 8081. I start it with the command:

npx expo start

I open it on my phone using the Expo Go app (SDK 52).

I’m trying to set up debugging in VS Code using Microsoft’s React Native Tools extension.

My .vscode/launch.json file looks like this:

{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Attach to Hermes application",
            "request": "attach",
            "type": "reactnativedirect",
            "cwd": "${workspaceFolder}"
        },
        {
            "name": "Debug in Exponent (LAN)",
            "request": "launch",
            "type": "reactnative",
            "platform": "exponent",
            "cwd": "${workspaceFolder}",
            "expoHostType": "lan"
        }
    ]
}

However, whenever I try to connect the debugger in VS Code, I always get:

Launching the application
Getting app.json path: c:/animalzap/client/react_native/app.json
Start parsing .json file...
An error occurred while launching the application. spawn EINVAL (error code 303)

any help? :(

2020-02-16T10:09:32Z

I'm running Visual Studio Code 1.42.1 on Ubuntu 19.10, using the default C# extension version 1.21.11.

Whenever I launch a C# program using "Start Debugging", or even via "Run Without Debugging", I see this message in the output window:

-------------------------------------------------------------------
You may only use the Microsoft .NET Core Debugger (vsdbg) with
Visual Studio Code, Visual Studio or Visual Studio for Mac software
to help you develop and test your applications.
-------------------------------------------------------------------

This message is annoying. Is there any way to disable it?

2023-03-03T01:14:51Z

I am trying to debug a Chrome Extension in VS Code using 'Attach to Chrome' configuration. However, when I run the debugger, it throws an error: "Cannot connect to the target at localhost:9222: Could not connect to debug target at http://localhost:9222: Could not find any debuggable target".

screenshot of the error message

Here is my launch.json:

{
  "version": "0.2.0",
  "configurations": [
    {
      "name": "Attach to Chrome",
      "port": 9222,
      "request": "attach",
      "type": "chrome",
      "webRoot": "${workspaceFolder}",
      "url": "https://github.com/",
    },
  ]
}

My manifest.json file includes the necessary content script and background script:

{
    "name": "Extension",
    "description": "Some description",
    "manifest_version": 3,
    "version": "1.0",
    "devtools_page": "devtools.html",
    "content_scripts": [{
        "matches": [
          "http://*/*",
          "https://*/*"
        ],
        "run_at": "document_idle",
        "js": [
          "content_script.js"
        ]
    }],
    "background": {
        "service_worker": "background.js"
    },
    "runtimeArgs": ["--load-extension=${workspaceFolder}"]
}

I have set the correct port number (9222) in my launch.json configuration file and enabled remote debugging in Chrome by running the following command in the terminal:

/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --remote-debugging-port=9222

Any suggestions on how to resolve this issue?

2024-04-30T23:27:19Z

After setting up Anaconda and VSCode on my new Mac and selecting my desired python interpreter (in this case called lotteryfl), it seems that a new terminal always starts with a base env activated on top of lotteryfl. This also applies when I try to start the debugger, so that my installed packages in lotteryfl cannot be found when being imported. How may I fix it so that only lotteryfl is activated?

2021-07-20T01:10:29Z

I'm very new to debugging. My whole programming "career" has been limited to inserting print statements to try to figure out why things aren't working the way I want them to. Now I'm trying to step through my Python code in Visual Studio Code, but when I try to step into the debugger, it jumps straight to the first exception (which is like 50 steps in to be clear).

I saw that there are debugging configurations, but surely I don't have to learn all about those just to step through the code. And I know you can set breakpoints, but I'd like to see each step for now. Is there something I'm missing? I was using IDLE to step through my somewhat simple function prior to trying VSCode, but all of the little tweaks made that way too slow. Thanks for any help you can provide.

As best I can tell, this is the configuration I'm using by default:

{
    // 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": [
        {
            "name": "Python: Current File",
            "type": "python",
            "request": "launch",
            "program": "${file}",
            "console": "integratedTerminal"
        }
    ]
}

2025-03-08T18:45:45Z

While coding and running an extension in debug mode, I get the error mentioned in the title.

Here is my extension.js:

// The module 'vscode' contains the VS Code extensibility API
// Import the module and reference it with the alias vscode in your code below
const vscode = require('vscode');

// This method is called when your extension is activated
// Your extension is activated the very first time the command is executed

/**
 * @param {vscode.ExtensionContext} context
 */

function getWebviewContent() {
    return `<!DOCTYPE html>
<html lang="en">
<head>
    <meta charset="UTF-8">
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <title>Video Player</title>
</head>
<body>
    <h1>Video Player</h1>
    <video width="640" height="360" controls>
        <source src="https://www.w3schools.com/html/mov_bbb.mp4" type="video/mp4">
        Your browser does not support the video tag.
    </video>
</body>
</html>`;
}

function activate(context) {

    // Use the console to output diagnostic information (console.log) and errors (console.error)
    // This line of code will only be executed once when your extension is activated
    console.log('Congratulations, your extension "YourApp" is now active!');
    
    let disposable = vscode.commands.registerCommand('extension.openVideo', function () {
        // Create and show a new webview
        const panel = vscode.window.createWebviewPanel(
            'videoView', // Identifies the type of the webview. Used internally
            'Video Player', // Title of the panel displayed to the user
            vscode.ViewColumn.One, // Editor column to show the new webview panel in.
            {
                enableScripts: true, // Enable JavaScript in the webview
                retainContextWhenHidden: true // Keep the webview's state even when it's hidden
            }
        );

        // Set the HTML content for the webview
        panel.webview.html = getWebviewContent();
    });

    context.subscriptions.push(disposable);
}

// This method is called when your extension is deactivated
function deactivate() {}

module.exports = {
    activate,
    deactivate
}

This is my package.json:

{
    "name": "financenews",
    "displayName": "FinanceNews",
    "description": "",
    "version": "0.0.1",
    "engines": {
        "vscode": "^1.98.0"
    },
    "categories": [
        "Other"
    ],
    "activationEvents": 
    [ 
        "onView:videoView", "onCommand:extension.openVideo" 
    ],
    "main": "./extension.js",
    "contributes": {
        "commands": [{
            "command": "financenews.helloWorld",
            "title": "Hello World"
        },
        {
            "command": "extension.openVideo",
            "title": "Open Video"
        }],
    "viewsContainers": {
        "activitybar": [
            {
                "id": "videoSidebar",
                "title": "Video Sidebar",
                "icon": "media/mario.svg"
            }
        ]
    },
    "views": {
      "videoSidebar": [
        {
          "id": "videoView",
          "name": "Video Player"
        }
      ]
    }
  },
  "scripts": {
    "lint": "eslint .",
    "pretest": "npm run lint",
    "test": "vscode-test"
  },
  "devDependencies": {
    "@types/vscode": "^1.98.0",
    "@types/mocha": "^10.0.10",
    "@types/node": "20.x",
    "eslint": "^9.21.0",
    "@vscode/test-cli": "^0.0.10",
    "@vscode/test-electron": "^2.4.1"
  }
}

I have tried the following things:

Used 'explorer' instead of 'videoSidebar'
Tried creating a class for VideoWebView and then tried to place getWebView() as a function inside the class.
Tried loading a video from a directory instead of using https://www.w3schools.com/html/mov_bbb.mp4 for source

2025-02-20T08:04:33Z

I am receiving the "error: unknown option: --interpreter=mi" when trying to debug with lldb in VS Code on Mac for C++, Clang Compiler, and an OpenMP implementation. I am unable to debug because of it. Below is the launch.json then tasks.json

{
  "version": "0.2.0",
  "configurations": [
      {
          "name": "Build with Clang and OpenMP",
          "type": "cppdbg",
          "request": "launch",
          "program": "${workspaceFolder}/CS267/tom_2.1/build/openmp",  // Path to compiled binary
          "args": [],
          "stopAtEntry": false,
          "cwd": "${workspaceFolder}/CS267/tom_2.1/",
          "environment": [],
          "externalConsole": false,
          "MIMode": "lldb",  // Use LLDB for debugging
          "setupCommands": [
              { "text": "-enable-pretty-printing", "description": "Enable pretty printing", "ignoreFailures": true }
          ],
          "preLaunchTask": "Build with Clang and OpenMP",
          "miDebuggerPath": "/usr/bin/lldb"  // Path to LLDB on macOS
      }
  ]
}

{
    "version": "2.0.0",
    "tasks": [
      {
        "label": "Build with Clang and OpenMP",
        "type": "shell",
        "command": "cmake",
        "args": [
          "--build",
          "${workspaceFolder}/CS267/tom_2.1/build"
        ],
        "group": {
          "kind": "build",
          "isDefault": true
        },
        "problemMatcher": ["$gcc"],
        "detail": "Generated task by debugging configuration."
      }
    ]
  }

I have tried editing the tasks.json and launch.json numerous times to no avail. Chat has not helped.

2025-10-29T20:26:10Z

I would like to know if there exists any way to interact programmatically with the vs code debugger during a session. Python would be ideal, but JS/TS could also work. For the langages being debugged (if relevant) would be C/C++ and Fortran.

My goal would be for instance to be able to dump some variables to a file with their values at different points of execution (like a trace), without having to alter the code or even detailing the structures myself (the debugger would allow this kind of 'reflection' for the structure, listing all the fields for me).

My current setup is working on Windows, targeting "cppvsdbg". I had left that point out because I was hoping to find a vscode-level solution, not caring so much about the backend: just query VS Code which already did the job of talking to the underlying debugger.

2022-02-10T13:37:14Z

I'm currently trying to get a better understanding of the embedded toolchain by leaving the common out-of-the-box IDEs and create my own inside of Visual Studio Code.

With the help of some tutorials I managed to get my blinky LED project for an STM32L433 Nucleo board up and running.

The last step I had to do was implementing the debug functionality. As I only did this via an IDE in the past this part is a bit tricky for me. Nonetheless I managed to get it work but I still have some problems of wrapping my head around what is actually going on.

Therefore I hope you guys can help me get a better understanding of this.

Im using Visual Studio Code with the C/C++ and Cortex-debug extensions. Hardwarewise I'm using a STM32L433 Nucleo-Board with the build in ST-Link debugger probe.

I created my project in VSC and created a launch.json for the debug settings, it looks like this:

{
    "version":"0.2.0",
    "configurations": [
        {
            "name": "Cortex ST-Link",
            "cwd": "${workspaceRoot}",
            "executable": "./build/Test.elf",
            "request": "launch",
            "type": "cortex-debug",
            "servertype": "stlink",
            "stlinkPath": "D:/CubeIDE/STM32CubeIDE_1.8.0/.../bin/ST-LINK_gdbserver.exe",
            "stm32cubeprogrammer": "D:/CubeProgrammer/bin",
            "device": "STM32L433RC",
            "configFiles": [
                "interface/stlink.cfg",
                "target/stm32l4x.cfg"
            ],
            "svdFile": "STM32L4x3.svd"
        },  
        {
            "name": "Cortex Debug",
            "cwd": "${workspaceRoot}",
            "executable": "./build/Test.elf",
            "request": "launch",
            "type": "cortex-debug",
            "servertype": "openocd",
            "device": "STM32L433RC",
            "configFiles": [
                "interface/stlink.cfg",
                "target/stm32l4x.cfg"
            ],
            "svdFile": "STM32L4x3.svd"
        }       
    ]

}

Both configurations work, I don't know if this is the right/professional way to do this but this is all I found from examples and the Cortex-debug documentation. If I did something wrong, please tell me what I should do differently.

What I learned thus far regarding Debugging is the following:

I need a debugging probe that can communicate with the debug access port of my MCU.
I need a GDB server that handles communication between the debugger and my PC.
And I need a client tool that connects to the GDB server and gives me an interface to read and write debug instructions and informations.

So lets start with the OpenOCD configuration. The used debugger is the st-link from the nucleo board. My GDB server would be OpenOCD and my client is the arm-none-eabi-gdb utility if I get this right from the debug console. I use the stlink.cfg to tell the server which debugger I use so it knows how to communicate with it. Is this correct this far?

Next the ST-Link config. Instead of OpenOCD I now use the ST-Link-GDB server. And for the client again the arm-none-eabi-gdb. But when I start to execute it like this, the ST-Link-GDB server throws an error that it can't find the STCubeProgrammer utility. So I also give the path to this utility and it works. My question now is, what is the CubeProgrammers role in this chain? I obviously doesn't need an additional component with OpenOCD, so why do I need the CubeProgrammer? I firstly thought that the CubeProgrammer is the client in this case but I can see that arm-none-eabi-gdb still gets called in this debug config. Even ST's GDB userguide only shows the server, debugger and client and no programmer in the overview...

Can someone help me understand what is going on behind the scene and what the role of the CubeProgrammer is? Or maybe point out if I have some false configuration/understanding in this matter?

Thanks in advance :)

Best regards

Evox402

2021-02-12T09:48:17Z

I am trying to get the debugger to work but I get the following error "Unable to start debugging. Not implemented.". I am a bit unsure on what that means let alone how to solve it.

My launch.json file looks like this:

{
    // 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": [
        {
            "name": "(Windows) Launch",
            "type": "cppvsdbg",
            "request": "launch",
            "program": "Assigment_1.C++",
            "args": [],
            "stopAtEntry": false,
            "cwd": "${workspaceFolder}",
            "environment": [],
            "console": "externalTerminal"
        }
    ]
}

2025-01-21T02:50:19Z

This is slowly driving me insane, but some inexplicable reason one of my workspaces in vscode has reverted the run button in the editor actions menu to run and debug, so every time I press it, it opens the debugger. I have tried everything I cannot find an option to just change it to run

this is how it looks now ^

How do i change it to this ^

2022-12-06T13:28:31Z

Whenever i try to debug it tells me "launch: program c:filepath\build\debug\outdebug" does not exist

launch.json

{
  "version": "0.2.0",
  "configurations": [
    {
      "name": "C/C++ Runner: Debug Session",
      "type": "cppdbg",
      "request": "launch",
      "args": [],
      "stopAtEntry": false,
      "externalConsole": true,
      "cwd": "c:/Users/name/CSC",
      "program": "c:/Users/name/CSC/build/Debug/outDebug",
      "MIMode": "gdb",
      "miDebuggerPath": "gdb",
      "setupCommands": [
        {
          "description": "Enable pretty-printing for gdb",
          "text": "-enable-pretty-printing",
          "ignoreFailures": true
        }
      ]
    }
  ]
}

task.json

{
    "tasks": [
        {
            "type": "cppbuild",
            "label": "C/C++: g++.exe build active file",
            "command": "C:\\MinGW\\bin\\g++.exe",
            "args": [
                "-fdiagnostics-color=always",
                "-g",
                "${file}",
                "-o",
                "${fileDirname}\\${fileBasenameNoExtension}.exe"
            ],
            "options": {
                "cwd": "${fileDirname}"
            },
            "problemMatcher": [
                "$gcc"
            ],
            "group": {
                "kind": "build",
                "isDefault": true
            },
            "detail": "Task generated by Debugger."
        }
    ],
    "version": "2.0.0"
}

c_cpp_properties.json

{
    "configurations": [
        {
            "name": "windows-gcc-x86",
            "includePath": [
                "${workspaceFolder}/**"
            ],
            "compilerPath": "C:/MinGW/bin/gcc.exe",
            "cStandard": "${default}",
            "cppStandard": "${default}",
            "intelliSenseMode": "windows-gcc-x86",
            "compilerArgs": [
                ""
            ]
        }
    ],
    "version": 4
}

I dont understand why i can run programs, but debugging gives me the errors. tried re-installing g++, same errors. Ive gone to the launch.json "program": "c:/Users/name/CSC/build/Debug/outDebug", file location and there is no build file much less a debug file so its being directed to a non-existent file location for some reason?

2025-10-19T14:03:35Z

I have the following simple php test file:

<?php
$a = 1 ;
$debug = true ;

This file has two linked filenames: testa and testa.php

I have set both of these files with a breakpoint at the third line ($debug = ....)

If I now invoke php testa.php, the script stops at line 3 and a mouseover of line 1's $a will reveal the value of $a (which is of course 1 at that point).

But if I instead invoke php testa, the script stops at line 3 and a mouseover of line 1's $a reveals the attributes of $a (int, etc) - but not a value. However, if I type $a into the debug console, I get the expected value of 1. I can also see the $a = 1 value in the Variables window, just not on mouseover.

Is VSCode actually, as it seems, functioning differently depending upon the extension of a filename? (I don't think VSCode should be enforcing rules about script naming standards. And, anyway, it seems weird that all other debug capabilities except this seem to work fine.)

If VSCode is doing that, is there a setting that I can use to control this?

2021-01-19T21:03:14Z

Just getting started with FastAPI, but running into issues with trying to get it to recognize breakpoints in the VSCode debugger. The strange thing is that it does successfully break on lines that are not contained within routes

Pulling directly from the tutorial: https://fastapi.tiangolo.com/tutorial/debugging/

import uvicorn
from fastapi import FastAPI

app = FastAPI()  # breakpoint here works on launching file
print('here')    # breakpoint here works on launching file


@app.get("/")
def root():
    a = "a"   # breakpoint here does NOT work
    b = "b" + a
    return {"hello world": b}  # returns data successfully


if __name__ == "__main__":
    uvicorn.run(app, host="0.0.0.0", port=5002)

As commented above, the lines outside the routes work fine, and when I go to the address I get the data successfully, but the breakpoint within the route does not fire. Not sure what I'm missing here. Have tried various solutions from Debug FastAPI application in VSCode

I'm not sure if this makes a difference, but this is also running through the Remote-SSH extension on VSCode (my code is on a gcloud VM). Maybe this is contributing but again, the other breakpoints fire fine.

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": [
        {
            "name": "Python: Current File",
            "type": "python",
            "request": "launch",
            "program": "${file}",
            "console": "integratedTerminal"
        }
    ]
}

EDIT: Looks like it does work if I replace "def" with "async def", though I'm trying to get this to work with a SQLite DB and per this page: https://fastapi.tiangolo.com/tutorial/sql-databases/ it recommends using "def" by default (with options to configure to use async def). I'll need to look into the distinction some more.

2025-05-22T01:22:00Z

I have written a cmdlet called Select-Blah.ps1 that extract certain information from log files. The log files are sent to my cmdlet via the pipeline:

PS> Get-Content log.txt | Select-Blah

How can I run the command above in the vscode debugger? Specifically, what launch configuration can I put into my launch.json file in vscode?

2021-11-12T01:24:05Z

I'm working on a React app in VSCode that's running on localhost:3000. I can visit the app in the browser. If I try to do ctrl+c in the terminal, an empty line is written but the app is still accessible. I need to close the app for some changes I'm planning to make. What's the best way to do this?

2021-04-27T15:03:31Z

I'm trying to run my program with GDB debugger. When I run it, I get a warning:

GDB: Failed to set controlling terminal: Operation not permitted

That warning appears and disappears very fast in my terminal. I already check some stackoverflow questions, but since I'm running visual studio attached to my docker (remote-container), I'm unable to apply some recommendations.

When I try a brake-point in my code, GDB does not work, and the program executes ignoring GDB.

My lauch.json configuration:

{
    // 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": [
        {
            "name": "(gdb) Launch",
            "type": "cppdbg",
            "request": "launch",
            "program": "${workspaceFolder}/words",
            "args": [],
            "stopAtEntry": false,
            "cwd": "${workspaceFolder}",
            "environment": [],
            "externalConsole": false,
            "MIMode": "gdb",
            "setupCommands": [
                {
                    "description": "Enable pretty-printing for gdb",
                    "text": "-enable-pretty-printing",
                    "ignoreFailures": true
                }
            ]
        }

    ]
}

The dockerfile configuration where I'm running my program:

FROM ubuntu:18.04

SHELL ["/bin/bash", "-c"]

RUN apt-get -y update
RUN apt-get install -y Linux-headers-generic build-essential gdb

COPY . /ejercicio

2022-01-27T12:26:25Z

I have recently started using VS code for Python development. I am unable to figure out how to launch an interactive terminal while debugging, with the program state loaded-in . For example, consider the following code,

import numpy as np
A = np.array([1, 2, 3])
B = np.zeros()
C = A/B                  \\ <--- Breakpoint here

I want to set a breakpoint at C = A/B and as soon as the breakpoint hit, I want to launch an interactive terminal that holds the state of my program. So that I can play around with variables in the terminal.

This is simple and straightforward in other Python IDEs like Spyder and Pycharm. How do I do this with VS Code?

2024-02-04T16:06:04Z

I debug the xv6 kernel in VS Code, but the debug console doesn't seem to support ANSI colors perfectly.I don't know how to make it display ANSI colors correctly.

What my Debug Console shows:

I have tried to find a solution to the problem, and I have noticed that this problem was mentioned in an issue of VS Code, and the issue has been solved by PR. I feel that my problem is similar to what is described in this issue, but I have not been able to solve it.

I also tried this in PR, and when I debugged the ts program, the Debug Console seemed to work fine. However, when I debug a C/C++ program (xv6 kernel), ANSI colors are not displayed correctly.

What my Debug Console shows when I tried to debug TypeScript file:

2025-09-20T19:10:11Z

I would like to know how to setup launch.json and tasks.json to close all relevant terminals after debugging session is stopped.

For example i run ASP.NET app and Stripe Webhook Listen in compound launch.json configuration.

But when i stop debugging stripe stays open and next time i run debugging it first asks me to stop stripe then i can restart it its so anoying.

I have added stopAll:true but that didnt help as well.

 "compounds": [
    {
      "name": "Launch With Stripe",
      "configurations": ["Launch AspNet With Proxy", "Stripe"],
      "stopAll": true,
      "presentation": {
        "hidden": false,
        "group": "",
        "order": 1
      }
    }
  ]

EDIT: added stripe tags maybe it is connected to the extension as well

2023-12-05T09:24:08Z

My teacher keep giving me Jupyter Notebook where the entire program is split to different cell for each class. The last cell, is the bootstrap code, creating an instance of the ~main class and calling a method on it.

I used Jupyter Notebook inside VS Code because the real Jupyter Notebook on a browser seems to be worst about debugging and code completion...

I don't find a way in VS Code to ask to debug the entire code, so that the code stop to any breakpoint set. The only workaround I found is to merge all the cells...

Without merging all the cells, if I debug the last cell with the bootstrap code, it will complain it doesn't find the class(es) because in different cell(s)...

2025-10-02T08:25:04Z

GDB console works well with gdbserver, but via VSCode it doesn't stop at breakpoints

"version": "0.2.0",
"configurations": [
    {
        "name": "(gdb) remoute",
        "type": "cppdbg",
        "request": "launch",
        "program": "${workspaceFolder}/hello",
        "cwd": "${workspaceFolder}",
        "targetArchitecture": "arm64", // Or "AArch64"
        "externalConsole": false,
        "MIMode": "gdb",
        "miDebuggerPath": "${workspaceFolder}/tools/gdb/host/gdb",
        "miDebuggerServerAddress": "100.1.1.150:10001"
    }   
]

I tried different versions of GDB, GDBSERVER, VSCode

2022-06-07T01:37:53Z

I am trying to run some solidity code but receiving this error on vs code. I am not sure what the issue is.

node version node:internal/modules/cjs/loader:942 throw err; ^

Error: Cannot find module '/Users/h/U_Block Developer/star/version' at Module._resolveFilename (node:internal/modules/cjs/loader:939:15) at Module._load (node:internal/modules/cjs/loader:780:27) at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12) at node:internal/main/run_main_module:17:47 { code: 'MODULE_NOT_FOUND', requireStack: [] }

I am on Mac Monterey OS.

Image here