microsoft / microsoft/vscode-cpptools
Breakpoints not hit when added during runtime with MinGW in VSCode
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
Environment
- OS and version: windows 11
- VS Code:
- C/C++ extension:
- OS and version of remote machine (if applicable):
- GDB / LLDB version: GNU gdb (GDB) 11.2
Bug Summary and Steps to Reproduce
Bug Summary:
When I run a GUI program (for example, a Qt application) in VSCode, if I add breakpoints during execution, they cannot be hit. However, in Qt Creator, the breakpoints can be hit under the same conditions. Both in Qt Creator and VSCode I am using the same MinGW 11 toolchain. I have tested across multiple environments and this problem consistently occurs.
Debugger Configurations
/
Debugger Logs
/
Other Extensions
/
Additional Information
The condition is that the breakpoints are added while the program is running, not when the program is paused.
Contributor guide
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 by reproducing the issue on Windows 11 with MinGW 11, GNU GDB 11.2, and a Qt GUI application in VS Code. Compare breakpoints added while the program is running with those added while paused, and verify that runtime-added breakpoints are hit; the issue names no source files or tests to inspect.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vscode
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100