ida: we leave behind unpacked database files
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6.2k
- Forks
- 726
- Avg merge
- 11d 11h
- Merged PRs (30d)
- 7
Description
> Note, in current version of capa (commit https://github.com/mandiant/capa/commit/6579e01d15a6dbfeead1393a197d9d813f393dab), because of the lack of idapro.close_database, running capa -b will cause idapro to leave behind unpacked database files (*.id0 *.id1 *.id2 *.nam *.til);
@young-lord
see original report in #2950
we should be using a context manager to open the database, rather than trying to manually track when to open/close the db.
Contributor guide
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 capa -b path where the IDA database is opened and compare its lifecycle with idapro.close_database. Review the original report in #2950 and verify that database handling uses a context manager; done means running this path no longer leaves behind unpacked *.id0, *.id1, *.id2, *.nam, or *.til files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- reverse-engineering
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100