inducer / inducer/pudb

Jump command

Open
#129 11 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Python
Stars
3.2k
Forks
245
Avg merge
13m
Merged PRs (30d)
5

Description

When researching the bug for https://github.com/inducer/pudb/pull/90, I read in the [docs](https://docs.python.org/3/reference/datamodel.html):

> f_lineno is the current line number of the frame — writing to this from within a trace function jumps to the given line (only for the bottom-most frame). A debugger can implement a Jump command (aka Set Next Statement) by writing to f_lineno.

I'm probably the last person to learn about this, but it seems like a useful thing to implement. `j` is already taken as down, but `J` is free. It's probably easy to implement, at least assuming the error reporting is good for bad jumps.

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue points to Python's frame f_lineno documentation and the related pull request #90; start by inspecting the debugger's existing command handling and error reporting. Determine how the free J key would invoke a Jump command, then verify valid and invalid jumps behave as intended.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
cli, devtools
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.