axodotdev / axodotdev/axocli

prettier backtraces

Open
#1 0 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Rust
Stars
16
Forks
0
PR merge metrics
No merged PRs in 30d

Description

We do some custom backtrace stuff in our panic hook (the relevant details being in panic.rs) and I don't really like the current output. It's very noisy, especially with printing the address of a frame even if we symbolicated it. That said I need to test it out in "production" environments where symbols are worse (no local debuginfo sitting in target/) to figure out what can be trimmed or not.

The situation isn't 1:1 (not using the backtrace crate) but minidump_processor has much prettier output with this more complex impl: https://github.com/rust-minidump/rust-minidump/blob/main/minidump-processor/src/process_state.rs#L737

Contributor guide

Open the contributing guide

Research direction

Start by reading panic.rs and compare its backtrace formatting with the referenced minidump_processor implementation. Exercise the panic hook in environments with and without local debuginfo to determine which frame details remain useful. Done means a less noisy backtrace presentation while retaining useful information when symbols are unavailable.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
cli
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.