microsoft / microsoft/vscode-cpptools
assertion failures are called exceptions
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
VSCode can give the misleading impression that a C++ exception has been thrown, when really all that happened was an assertion failure when using the assert() function. The call stack also says "PAUSED ON EXCEPTION" (If I recall correctly Visual Studio says "Debug Assertion Failed!")
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
Reproduce the issue in VS Code using a C++ program with assert() and inspect how the C/C++ extension presents the paused state and call stack. Compare the displayed wording with the reported behavior; done means assertion failures are clearly distinguished from C++ exceptions and the misleading “PAUSED ON EXCEPTION” label is removed or corrected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, typescript
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100