Vector35 / Vector35/binaryninja-api
Analysis sometimes stuck at "Parsing debug info..." with debuginfod enabled
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 19
Description
Sometimes the remote request just gets stuck, there is no way to cancel this, and the background task is stuck indefinitely until the application is restarted.
We need to set some timeout here, and we need to be able to actually cancel the debug info parsing.
I am considering this a deadlock, since there is no way to get out of this broken state for the view instance, you can of course disable debuginfod.
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 at plugins/dwarf/dwarf_import/src/helpers.rs lines 450-461, then trace the debuginfod request and debug-info parsing path. Check how the remote request currently waits and whether parsing has a cancellation path. Done means a stuck request times out and debug-info parsing can be cancelled without restarting the application.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- reverse-engineering
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100