Support manually refreshing the memory region
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 331
- Forks
- 33
- PR merge metrics
- No merged PRs in 30d
Description
In light of https://github.com/Vector35/debugger/issues/1158, we might have to change the default of debugger.useMemoryMapSegments to false. This would cancel the benefits of having the memroy regions info in various cases, so we might wish to have a way to manually refresh that info
Though we need to be careful -- since the way we apply memroy regions as segments on the binary view affect the ability to read memory bytes, so we need to make sure when the user does a manual refresh of the memory region, all memory cache are all discarded
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 tracing the debugger.useMemoryMapSegments setting and the code that applies memory regions as binary-view segments. Determine where a manual refresh should enter and how memory caches are discarded; done means refreshed region information is applied without leaving stale cached memory bytes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- reverse-engineering
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100