microsoft / microsoft/vscode-cpptools

Random error 'Exception has occurred' gets quite frequent

Open
#2,441 4 comments 0 reactions 1 assignee View on GitHub

@pieandcakes is already working on this.

Since Aug 29, 2018.

debugger
Dominant language
TypeScript
Stars
6.2k
Forks
1.7k
Avg merge
14h 46m
Merged PRs (30d)
61

Description

Type: Debugger
Input information below

Please review existing issues and our documentation at https://github.com/Microsoft/vscode-cpptools/tree/master/Documentation prior to filing an issue.

Describe the bug

  • OS and Version: MacOS High Sierra, Version 10.13.6
  • VS Code Version: 1.26.1
  • C/C++ Extension Version: 0.18.1
  • Other extensions you installed (and if the issue persists after disabling them): No other extension
  • A clear and concise description of what the bug is. I got a random error mentioning 'Exception has occurred.' when stepping forward in a multi-thread environment. It doesn't show in a single thread environment.

To Reproduce
Please include a code sample and launch.json configuration.
Steps to reproduce the behavior:

  1. Check out this project https://github.com/JerryCao1985/SORT
  2. Compile it. It is simple to compile it because I already have the VSCode task to compile it.
  3. Unzip the attached file in bin folder so that there is a folder named 'intermediate' in bin folder. intermediate.zip
  4. Try debugging the program by placing a breakpoint in PathTracing::Li
  5. When stepping forward, you get pretty frequent error mentioning 'Exception has occurred.' It doesn't stop anything but is really annoying.

Additional context
If applicable, please include logging by adding "logging": { "engineLogging": true, "trace": true, "traceResponse": true } in your launch.json
Add any other context about the problem here including log or error messages in your Debug Console or Output windows. There is no any other error output at all.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.