Vector35 / Vector35/debugger

Add comment feature that explains what breakpoint is set for

Open
#403 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

This is not a bug report, but a request to add a feature.

Binary ninja has a feature for writing comments in Main View, but I think this is mainly used to write what the code does.
Break points are set temporarily, but if I set many break points, I may forget what the break point is for.
So I request to add the function to write comments on break points.

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

Start by reviewing the debugger's breakpoint handling and the existing Main View comment feature. Clarify how a comment should be attached to, displayed with, and removed from a breakpoint; done means users can identify the purpose of each breakpoint through its comment.

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
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.