Provide visual indicator of current TTD trace filename
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 331
- Forks
- 33
- PR merge metrics
- No merged PRs in 30d
Description
Binary Ninja must provide context of what TTD trace is currently running, likely just as the name of the .run file (with .run extension removed or retained).
Use case: I am debugging an application that requires input during operation. I create a TTD trace file for each of the various inputs I choose. During long periods of debugging, I need a visual reminder of which exact trace file I am in.
Current workflow:
Record TTD trace
Rename the .out, .run files to specify the inputs I provide, such as 00000., 10000., 31337.*
I run TTD debugging and choose the specifc trace I want.
I go to sleep and wake up forgetting which trace I was looking at.
What is required:
Visual indicator in the UI of which specific trace I am tracing. Suggestions:
- In bottom status bar, left, next to debugger status (running, stopped at 0xX)
- In PE triage
- In Windows title
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the debugger UI locations named in the issue: the bottom status bar, PE triage, and Windows title, then determine how the selected TTD .run trace filename is exposed. Done means the active trace's filename is visibly identified while debugging, with the chosen display location and extension behavior resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop, reverse-engineering
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100