DEBUGGER_.warn when skipping breakpoint because of RUBY_DEBUG_SKIP_PATH
还没有人认领这个 Issue。
评估
调研方向
Start by tracing how RUBY_DEBUG_SKIP_PATH affects breakpoint handling in the debugger. Add coverage for a breakpoint in a skipped path and verify that DEBUGGER_.warn is emitted only when the breakpoint would otherwise stop; run the relevant debugger tests to confirm the warning.
由索引模型根据 Issue 内容生成。
描述
Your proposal
If a user sets a breakpoint in a path that is skipped because of RUBY_DEBUG_SKIP_PATH, it would be helpful to log a warning whenever the breakpoint would have stopped if the configuration wasn't there.
Additional context
Sometimes I set up RUBY_DEBUG_SKIP_PATH for the most common case, but eventually end up having to dig deeper than usual, and add a breakpoint in a skipped path. After the debugger failing to stop there for a couple of times, I realize the problem and change the configuration.
It would be useful for the debugger to tell me that I have a breakpoint in a skipped path, to help me realize my error faster.
- 主要语言
- Ruby
- 星标
- 1.3k
- 派生
- 146
- PR 合并指标
- 30 天内没有已合并 PR
贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
ruby/debug 的其他 Issue
-
难度 3/5 1-2 天 新手友好度 68/100
-
Support exceptionOptions in setExceptionBreakpoints to catch arbitrary exception classes via DAP 未关闭
难度 4/5 3-5 天 新手友好度 55/100
-
难度 3/5 1-2 天 新手友好度 45/100
-
难度 4/5 3-5 天 新手友好度 52/100
-
难度 4/5 3-5 天 新手友好度 35/100
相似的 Issue
-
难度 1/5 1 小时以内 新手友好度 90/100
-
难度 2/5 1-3 小时 新手友好度 88/100
-
バグ
难度 1/5 1 小时以内 新手友好度 92/100
-
难度 2/5 1-3 小时 新手友好度 75/100
voxpupuli/puppet-epel#186 · 1 条评论 ·
-
external_created_at is no longer used for the message timestamp since the new message UI (v4.4.0) 未关闭Bug Frontend
难度 2/5 1-3 小时 新手友好度 78/100