Vector35 / Vector35/debugger

Support running a comamnd when a breakpoint is hit

Open
#319 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

breakpoint Effort: High enhancement functionality Impact: High
Dominant language
C++
Stars
331
Forks
33
PR merge metrics
No merged PRs in 30d

Description

This issue has no description.

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.

Research direction

The issue names no files, tests, or entry points. Start by locating the debugger's breakpoint-hit handling and command execution paths, then determine the expected command syntax and lifecycle from existing behavior. Done criteria are not specified beyond supporting a command when a breakpoint is hit.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
devtools, reverse-engineering
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.