microsoft/vscode-cpptools

Environment OS and Version: Windows VS Code Version: 1.122.0 C/C++ Extension Version: 1.32.2 If using SSH remote, specify OS of remote machine: Rocky 10 When debugging an cpp application under linux/gdb, then arguments are passed to the gdb without single quotes. For example "args": [ "\\\\srv\\path1\\path2\\file.txt" --> in gdb, this arguments arrives as: -exec p argv[1] $1 = 0x7fffffffd937 "\\srvpath1path2file.txt" Putting the argument in additional single quotes is a workaroung when debugging with gdb (but not when debugging on Windows) "args": [ "'\\\\srv\\path1\\path2\\file.txt'" ==> The cpptools-Extension should quote parameters with a single quote (') Bug Summary and Steps to Reproduce Bug Summary: Steps to reproduce: Go to '...' Click on '....' Scroll down to '....' See error Expected behavior: Configuration and Logs =thread-group-added,id="i1" GNU gdb (Rocky Linux) 16.3-2.el9 Copyright (C) 2024 Free Software Founda

Environment OS and version: Linux Mint 22.3 (inside Distrobox) VS Code: 1.114.0 (e7fb5e96c0730b9deb70b33781f98e2f35975036) C/C++ extension: 1.32.2 GDB version: 15.1 Bug Summary and Steps to Reproduce Bug Summary: As far as I understand, IDE + GDB should not call "children" method of a pretty-printer unless the user has asked to expand the value in GUI. Moreover, calling "children" method recursively is unacceptable, because linked data structures can be expanded infinitely. And this is exactly what I see happening in this case: GDB recursively traverses the data structure and hangs because it has loops. Steps to reproduce: Clone this repository: https://github.com/stgatilov/vscode-gdb-pretty-printers-hangs-repro-code Open it in VS Code. Build Debug build. Put breakpoint at the only line of badfunc. Run debugging using the included configuration "Launch with pretty printers". When debugger stops at the breakpoint, GDB hangs trying to evaluate local variable entity. Debugger Configur

Environment OS and Version: Microsoft Windows 10 Pro (Version 10.0.19045 Build 19045) VS Code Version: 1.119.0 C/C++ Extension Version: 1.32.2 Visual Studio Version: Community 2026 version 18.5.2 Bug Summary and Steps to Reproduce Bug Summary: When AddressSanitizer throws an exception, VS Code breaks but tries to open a file "vcasan.cpp" which can't be found. By going to the debug Call Stack I can select the main.exe!main() Line 5 frame to see the actual line in my source code that caused the overflow, but I'm wondering if I've misconfigured something that would let VS Code do this automatically? Any help is appreciated, thanks! Steps to reproduce: Download and unzip example code: AddressSanitizerTest.zip Launch VS Code from x64 Native Tools Command Prompt for VS Open example code Run default build task Start debugging Address Sanitizer throws exception, but VS Code shows unhelpful The editor could not be opened because the file was not found. message Expected behavior: VS Code b

Environment OS and version: Ubuntu 25.10 VS Code: 1.117.0 C/C++ extension: 1.5.1 OS and version of remote machine (if applicable): GDB / LLDB version: 16.3 Bug Summary and Steps to Reproduce Bug Summary: When the debugger stops at a breakpoint, the entire VSCode just focuses on the code editor. Can't do anything in other windows, watch window for instance. Can't even interact with the VSCode menu at all! Steps to reproduce: In this environment... With this config... Do '...' See error... Debugger Configurations `launch.json`: { "name": "C++ Launch (Console)", "type": "cppdbg", "request": "launch", "preLaunchTask": "CMake: build all", "postDebugTask": "", "program": "${workspaceFolder}/Debug/Console", "cwd": "${workspaceFolder}/build", "stopAtEntry": false, "externalConsole": false, "launchCompleteCommand": "exec-run", "linux": {

Environment VS Code version: 1.115.0 cpptools extension: ms-vscode.cpptools 1.31.4 OS: Windows 11 Compiler: MSVC (Visual Studio Community 2022, amd64) CMake Kit: Visual Studio Community 2022 Release - amd64 Bug Description When debugging a C++ project built with MSVC (VS2022), std::unordered_map<int, float> values are displayed as (,) in both the hover tooltip and the Variables/Watch panel. Steps to Reproduce Declare and populate a std::unordered_map<int, float> variable. Start debugging (via CMake Tools, using cppvsdbg). Hover over the variable or expand it in the Variables panel. Expected Behavior Each entry should display as [key] = value, e.g. [3] = 0.5. Actual Behavior Each entry displays as [3] = (, ). Additional Notes begin()->first and begin()->second both evaluate correctly in the Watch panel, so debug info is intact. The issue appears to be that std::pair::DisplayString expressions ({first}, {second}) fail when rendered as part of unordered_map expansion in vsdbg's natv