Ignore Certain Exceptions while Debugging

未关闭
#2,374 7 条评论 7 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
25/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
cpp, typescript, vscode
领域
devtools

调研方向

该 issue 未指出任何实现文件或测试。首先跟踪 C/C++ 扩展如何处理“All Exceptions”断点设置和异常暂停;将调试控制台的行为与执行停止进行比较。完成标准是:用户可以忽略选定的异常类型,或者在禁用所有异常中断时,确实能够在发生异常时继续执行而不停止。

由索引模型根据 Issue 内容生成。

描述

debugger

Type: Debugger

  • OS and Version: Windows 10 Enterprise x64
  • VS Code Version: 1.25.1
  • C/C++ Extension Version: 0.17.7
  • Other extensions you installed (and if the issue persists after disabling them): N/A

There currently doesn't appear to be a way to ignore/skip breaking on specific exceptions when debugging.

In my specific use case, an Antivirus DLL is injected (beyond my control) that monitors and regulates memory access, and causes a large number of access violation errors in OS libraries.
log

These errors don't seem to cause functional issues with the program, and I can step over them to continue, but there are often 10, 20, or more steps that cause violations per line in the code I write, and it very quickly becomes unreasonable.

This is with the "All Exceptions" box unchecked, when checked the errors are not logged to the debug console, but execution is still paused and so I am presented with the same problem.
stack

Being able to even truly ignore all exceptions and only stop on breakpoints (as mentioned, execution is till paused on thrown exceptions with the "All Exceptions" breakpoint checkbox left clear) would be beneficial, but the ability to specifically ignore types of exceptions would be preferential.

Apologies if this is an existing feature or if an issue was already opened, I spent a good couple of hours digging for a solution and checking to make sure it wasn't already a requested feature and didn't see anything, but I'm new to issue reporting and may have overlooked something.

主要语言
TypeScript
星标
6.2k
派生
1.7k
平均合并
14 小时 46 分钟
30 天内合并 PR
61

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

microsoft/vscode-cpptools 的其他 Issue

查看 microsoft/vscode-cpptools 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。