Offer to apply soft patches to the target every time the target is launched
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 331
- Forks
- 33
- PR merge metrics
- No merged PRs in 30d
Description
Normally when the user wish to alter the program behavior at runtime, they can do it in two ways:
- Patch the analysis before debugging, save the patched file to disk, and debug the patched file
- Debug the original file, and apply patches at runtime. The patches will be lost after debugging
I am thinking that maybe we should offer a "soft patch", that is a patch applied every time when we launch the target. In this way, the user would not need to save the files to disk repeatedly, and they can easily turn patches on/off according to their need
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
The issue does not name a file, test, or entry point. Start by tracing how the debugger launches the target and how runtime patches are currently applied, then clarify how soft patches should be stored and toggled. Done means patches can be reapplied on each launch without modifying the original file and can be turned off.
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
- Mostly clear
- Newbie friendliness
- 35/100