matthiaskrgr / matthiaskrgr/icemaker
backtraces
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 88
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
I need to be able to run icemaker with backtraces (for reasons... :/ ) potentially without them leaking into all the rustc/tool invocations.
set RUST_BACKTRACE=SOME_VAR in every std::process::command::run ?
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 std::process::Command execution paths used by icemaker and its rustc/tool invocations. Determine how backtraces should be enabled for icemaker without leaking the setting into child tools; done when the requested backtrace behavior works with isolated child-process environments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers, devtools
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100