@d-e-s-o @ work
@d-e-s-o @ work
If we look at the `stat` type's definition for different platforms, we see: - [x86_64-unknown-linux-gnu](https://rust-lang.github.io/libc/x86_64-unknown-linux-gnu/doc/libc/struct.stat.html): ```rust st_dev: dev_t st_ino: ino_t [...] ``` - [aarch64-linux-android](https://rust-lang.github.io/libc/aarch64-linux-android/doc/libc/struct.stat.html): - same But for [arm-linux-androideabi](https://rust-lang.github.io/libc/arm-linux-androideabi/doc/libc/struct.stat.html) we...
Introduce the cc_test_so() helper function in order to get rid of all the arguments necessary for compiling this test binary.
Prototype for integration with https://lore.kernel.org/bpf/[email protected]/
We may want to consider switching to using the `goblin` crate for our ELF parsing needs. As per my understanding it is stable and used in many contexts. Doing so...
We could consider adding an API to `blazesym-c` for capturing traces emitted by the main crate. That could help with understanding of problems when even `blaze_err` is not sufficient. I...
Currently we only populate caches as part of the symbolization (or inspection) process. However, it may be beneficial to add support for pre-populating caches, so that symbolization (or inspection...) can...
We should capture some numbers on how `blazesym` compares to `llvm-symbolizer` in terms of performance (symbolization time + memory usage).
We should consider whether we want/need to support [mini debug information](https://sourceware.org/gdb/onlinedocs/gdb/MiniDebugInfo.html). Potentially relevant: https://github.com/iovisor/bcc/pull/4250