rust-lang / rust-lang/backtrace-rs
Support debuginfod
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 628
- Forks
- 291
- PR merge metrics
- No merged PRs in 30d
Description
There's a mention of debuginfod in the code from #427 (cc @philipc). I suggest we also add support for looking up in debuginfod.
If DEBUGINFOD_URLS is set, the the debug info can be obtained from:
{URL}/buildid/{BUILD_ID}/debuginfo
The simplest option is to call out to debuginfod-find. Another option is to download the file directly, but then you also need to think whether to cache it and where. LLVM uses a separate directory from debuginfod-client, for example.
Both options are likely to have issues with sandboxing. Thinking of sentry use-case, the panic handling thread probably has network access to send the report, so downloading might be more feasible than shelling out.
I can probably find time to work on this if there's a consensus how to best implement this.
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 reviewing the existing debuginfod mention from issue #427 and the DEBUGINFOD_URLS and debuginfod-find paths described here. Resolve whether direct downloading or invoking debuginfod-find fits the panic-handling and sandboxing constraints, including caching. Done means backtrace debug information can be retrieved from configured debuginfod services with appropriate tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100