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
-
難度 2/5 1-3 小時 新手友好度 75/100
simp/pupmod-simp-simp#395 ·
-
難度 2/5 1-3 小時 新手友好度 80/100
simp/pupmod-simp-rsyslog#219 ·
-
難度 1/5 1 小時以內 新手友好度 90/100
simp/pupmod-simp-pupmod#256 ·
-
難度 1/5 1 小時以內 新手友好度 90/100
simp/pupmod-simp-sudo#150 ·
-
難度 1/5 1 小時以內 新手友好度 90/100