Add "Step Call" button

Open
#1,191 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
cpp
Domain
devtools, reverse-engineering

Research direction

The issue names no files, tests, or entry points. Start by locating the debugger's existing step-into and step-return handling, then trace how execution stops at instruction boundaries. Done means a Step Call action runs until the next call instruction and is covered by appropriate debugger tests.

Written by the indexing model from the issue text.

Description

enhancement

What is the feature you'd like to have?
A "step call" button in the debugger would be very useful, this would execute the program until the next call instruction is hit.

Is your feature request related to a problem?
No

Are any alternative solutions acceptable?
AFAIK, this functionality is the best option for this kind of task.

Additional Information:
I would use this when I don't know the real entry point of the program, since step return is generally never hit because there is no return, and step into can be very slow if the program is big, Step Call would cut debugging time in half for a lot of situations where finding a specific call is the priority.

Dominant language
C++
Stars
331
Forks
33
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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 Vector35/debugger

All issues in Vector35/debugger

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.