@d-e-s-o @ work
@d-e-s-o @ work
This requires Rust `1.81` and, hence, will have to wait until `1.86` is released, as per our MSRV policy.
cc @jfernandez
The main purpose of the PR, at this point, is to get feedback on the idea and to motivate the inclusion of some of the preparatory changes (that are improvements...
> Do you want us to take a look now? Or do you expect to make more changes still in draft mode? It's not yet ready for review, mostly just...
Also, as a general question: I see that `bcc` supports pulling debug info/binaries using `debuginfod`. Blazesym doesn't support `debuginfod` directly. Rather, it's a building block on top ([example](https://github.com/libbpf/blazesym/tree/main/examples/sym-debuginfod)). Is the...
Closing this PR in favor of #3760.
While at it, let's also think about https://docs.rs/libbpf-rs/latest/libbpf_rs/struct.MapInfo.html and whether we want a `ProgramInfo` similar to it.
> > Seems now I am forced to DwarfSections::borrow_with_sup again, which allocates a new Arc with a sup which seems consistently worse than what was possible beforehand, right? > >...
> Can you demonstrate with some code? Here is an example: ```rust let sections = gimli::DwarfSections::load(/* .. */).unwrap(); let dwarf = if let Some(...) = /* maybe-some-sup-object */ { let...
Yep, either should work for the use case at hand. Thanks!