Repository navigation
1.23.5+: cppdbg is no longer compatible with CentOS 7 and RHEL 7 #13219
Description
Environment
- OS and version: Mac OS Sequoia 15.3
- VS Code: 1.96.4
- C/C++ extension: 1.23.5
- OS and version of remote machine (if applicable): CentOS Linux 7.3
- GDB / LLDB version: GDB 10.2-6.el7
Bug Summary and Steps to Reproduce
Bug Summary:
cppdbg not launching anymore. When clicked on the green arrow to start the debugger, a clock shows on the debug button on left side bar and disappears right away. There is nothing in the DEBUG CONSOLE and no related log messages anywhere. I don't know exactly what's wrong.
How do I figure out why the debugger doesn't start?
Steps to reproduce:
- In this environment...
- With this config...
- Do '...'
- See error...
Debugger Configurations
{
"name": "UnitTest",
"type": "cppdbg",
"request": "launch",
"program": "${workspaceFolder}/cmake-build-debug/PMGUTestApp",
"cwd": "${workspaceFolder}",
"stopAtEntry": false,
"externalConsole": false,
"MIMode": "gdb",
"miDebuggerPath": "/opt/rh/devtoolset-11/root/usr/bin/gdb",
"setupCommands": [
{
"description": "Enable pretty-printing for gdb",
"text": "-enable-pretty-printing",
"ignoreFailures": true
}
]
},Debugger Logs
There is no debugger logsOther Extensions
No response
Additional Information
No response
Activity
sean-mcmanus commentedon Jan 31, 2025
There's also a discussion thread with 2 other users reporting this on CentOS 7 at #13213 (reply in thread) .
[-]cppdbg stopped working[/-][+]1.23.5: cppdbg stopped working on CentOS 7[/+]github-actions commentedon Feb 1, 2025
Thank you for reporting this issue. We’ll let you know if we need more information to investigate it. Additionally, if you're working with GDB/LLDB, please note that the code is open source at https://github.com/microsoft/MIEngine/wiki/Contributing-Code . Your contributions are always welcome and appreciated.
7 remaining items
[-]1.23.5: cppdbg stopped working on CentOS 7 and RHEL 7[/-][+]1.23.5+: cppdbg is no longer compatible with CentOS 7 and RHEL 7[/+]github-actions commentedon Feb 7, 2025
This issue has been closed because the described behavior was determined to be by design.
ScanderDevMode commentedon Mar 1, 2025
Solution : Use the version 1.22.11 of cpp tools extension. That one was the last one available which worked on CentOS7, since it was using the older GLIBC lib.
Steps to Downgrade:
Posting this here if anyone stumbles here.
MikeWang000000 commentedon Apr 20, 2025
I made a patched version of VS Code Server linking to latest glibc & libstdc++.
vscode-cpptools can run on it smoothly too.
It is open source:
https://github.com/MikeWang000000/vscode-server-centos7