Debugger should make the creation of function at the current addrsss optional

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
cpp
Domain
devtools, reverse-engineering

Research direction

No files or tests are named. Start by tracing the debugger behavior that creates a function when execution stops at an address, then reproduce it while stepping backward through a TTD trace. Done means function creation can be disabled or made optional so backward stepping does not produce many one-instruction functions.

Written by the indexing model from the issue text.

Description

enhancement Impact: Low TTD

When the target stops at an address and there is no function for it, the debugger will create a function at the address to allow the display of disassembly/ILs. This works well in most cases, however, when it comes to TTD backward debugging, stepping backwards in the code will create various function that only has one instructions in it, which severely limits the readability.

While a better approach for this would be to backward scan the execution trace to find the call/jmp instruction that leads to the function, but for now we might need a workaround for it.

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.