**Environment** - OS and Version: Linux 5.15.0-164-generic #174-Ubuntu - VS Code: Version: 1.108.0 - `ms-vscode.cpptools`: 1.29.3 - GDB: 17.0.90 - GCC: 15.2.1 **Bug Summary and Steps to Reproduce** MiEngine fails to start a debugging session on a basic C++ project with GDB `17.0.90`. Attaching to a running process works fine though. To reproduce (on Linux): - Untar the attached archive - Make GCC available in your `PATH` - Build the program through `Ctrl+Shift-B` (`"C/C++: gcc build main` task) - Go to the VS Code *Debug Panel* and run the debugger The debugger will fail to start due to a Segmentation Fault. I have attached the log file in the archive (`gdb-vscode.log` file). Note that everything works fine with GDB `16.3`, so I suspect that the MiEngine is not fully adapted to changes that have been made in GDB 17. [cpp_project.zip](https://github.com/user-attachments/files/24591833/cpp_project.zip)
Environment
ms-vscode.cpptools: 1.29.3Bug Summary and Steps to Reproduce
MiEngine fails to start a debugging session on a basic C++ project with GDB
17.0.90. Attaching to a running process works fine though.To reproduce (on Linux):
PATHCtrl+Shift-B("C/C++: gcc build maintask)The debugger will fail to start due to a Segmentation Fault. I have attached the log file in the archive (
gdb-vscode.logfile).Note that everything works fine with GDB
16.3, so I suspect that the MiEngine is not fully adapted to changes that have been made in GDB 17.cpp_project.zip