Could use some more verbose output regarding the current state.
- Dominant language
- C++
- Stars
- 8.6k
- Forks
- 1k
- PR merge metrics
- No merged PRs in 30d
Description
Currently decompiling an old binary that I lost the source to but have the PBD, though 96 hours in it just seems to be allocating more memory rather than doing any useful work. Would it be possible to provide a little more info on what the current stage is doing (i.e. if it's allocating for a good cause or just stuck in a loop and leaking memory).
Contributor guide
No contributing guide indexed for this repository
Research direction
No source files, tests, or entry points are named in the issue. Start by reproducing the long decompilation with the supplied PDB and inspect RetDec's existing progress output and memory behavior. Done means users can distinguish the current processing stage from a stuck or leaking run.
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
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100