oxidecomputer / oxidecomputer/propolis
want DWARF information for production propolis-server binary
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 270
- Forks
- 42
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 6
Description
In investigating issues with guest disks, I found that our production binaries do not have useful DWARF information in them. Our current support for post-mortem debugging of rust binaries generally could be improved (and I have some specific ideas for things that would be useful to do specifically for propolis-server). Still, as our support for post-mortem debugging of rust binaries improves, we may want to debug old core files, and we will need the DWARF to do that.
I was able to build a propolis-server binary with DWARF using the debug flag in a cargo profile. We could also consider shipping the DWARF data separately from the binary. But I think we are going to want this data somehow.
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 locating the Cargo profile and production build configuration for the propolis-server binary, then inspect how the debug profile flag affects DWARF output. Compare retaining DWARF in the binary with shipping it separately, and define the production artifact needed for post-mortem debugging of old core files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100