bnjbvr/gimli — explained in plain English
Analysis updated 2026-07-18 · repo last pushed 2021-02-20
Build a custom debugger that reads DWARF data to show source lines and variable names.
Write a tool like addr2line that maps crash memory addresses back to source code locations.
Build a profiler or crash analyzer that needs to understand what's in a compiled binary.
Make debugging information human-readable for troubleshooting compiler behavior.
| bnjbvr/gimli | 0verflowme/alarm-clock | 0verflowme/seclists | |
|---|---|---|---|
| Language | — | CSS | — |
| Last pushed | 2021-02-20 | 2022-10-03 | 2020-05-03 |
| Maintenance | Dormant | Dormant | Dormant |
| Setup difficulty | hard | easy | easy |
| Complexity | 4/5 | 2/5 | 1/5 |
| Audience | developer | vibe coder | ops devops |
Figures from each repo's GitHub metadata at analysis time.
Requires a companion library like object to extract DWARF sections before passing data to gimli.
A fast Rust library for reading DWARF debugging information from compiled binaries, so tools like debuggers and crash analyzers can look up source lines and variable names without copying data around.
Dormant — no commits in 2+ years (last push 2021-02-20).
License is not stated in the available content.
Setup difficulty is rated hard, with roughly 1h+ to a first successful run.
Mainly developer.
This repo across BitVibe Labs
double-check against the repo, no cap.