microsoft / microsoft/MIEngine
MiEngine fails to start GDB 17
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 859
- Forks
- 233
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 3
Description
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 maintask) - 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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the attached gdb-vscode.log and reproduce the failure from the VS Code Debug Panel using GDB 17.0.90, then compare the startup behavior with GDB 16.3. Done means the basic C++ debugging session starts successfully on Linux with GDB 17 while process attachment continues to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, linux, vscode
- Domain
- devtools, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100