Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

DEBUGGER_.warn when skipping breakpoint because of RUBY_DEBUG_SKIP_PATH

Open
#996 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
ruby
Domain
devtools

Research direction

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.

Written by the indexing model from the issue text.

Description

enhancement

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.

Dominant language
Ruby
Stars
1.3k
Forks
146
PR merge metrics
No merged PRs in 30d

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.

More from ruby/debug

All issues in ruby/debug

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.