Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Add "Step Call" button

未关闭
#1,191 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
38/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
cpp

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.

主要语言
C++
星标
334
派生
33
平均合并
3 天 21 小时
30 天内合并 PR
5

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

Vector35/debugger 的其他 Issue

查看 Vector35/debugger 的全部 Issue

相似的 Issue

更多 C++ Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。