gimli

Author here, a bit cringe to see your WIP project posted here. My motivation for writing this from scratch is to simultaneously understand DWARF 5 in all its gory details, develop tooling to support my work on the OCaml compiler, and to build a source debugger in OCaml. The performance or lack of isn't a focus right now, I'm sure it doesn't compare to gimli-rs for performance but it does fully support DWARF 5 which gimli-rs doesn't (missing debug_info section support https://github.com/gimli-rs/gimli/pull/807). Currently I'm working on the read support, and various bits of tooling around understanding Call Frame Information and simulating the DWARF expression evaluation. I'm unhappy with the tooling GDB/LLDB provide for displaying and debugging this information, I've personally spent far too much time staring at CFI expressions and walkin

How does this compare with gimli-rs? Last I checked it was the absolute leader in performance. https://github.com/gimli-rs/gimli

I haven't blogged about this yet, but we saw a 1000x fold speed-up doing several things around symbolication. The more optimal approach we found was to use the gimli crate[1] directly & carefully optimize it to read in the data structures for the executable(s) you are symbolicating upfront & then issuing in-process queries. They also have a drop-in replacement of addr2line that outperforms it (both in symbolication speed & memory usage). I am curious about how that compares with libbfd since that wasn't under consideration for us as it uses GPLv3. [1] https://github.com/gimli-rs/gimli [2] https://github.com/gimli-rs/addr2line

It's also the name of a DWARF parser[1] which makes the best use of the name imho ;). This project is cool though! [1] https://github.com/gimli-rs/gimli