@d-e-s-o @ work
@d-e-s-o @ work
Seeing the same issue. Also, I am not sure if "user error" is the right connotation here. The trait seems pretty broken if you ask me, as it appears to...
> I looked at the change in blazesym is why the lossy conversion step would be needed in the first place? Because `convert_error` was not available for `&[u8]` inputs? Yes,...
I don't believe we have multi attach hooked up yet. Feel free to contribute the bindings.
Makes sense to me. Please feel free to open a pull request if you have something working.
> I suppose we could start with a `T: Sized` approach and also provide a few defs. That way we have some baked in forward compat. That sounds good to...
To give an update: This issue has been mitigated in some part by https://github.com/libbpf/libbpf-rs/commit/a00ee2d5e0834c7f8764006689321dd4bca8653a and https://github.com/libbpf/libbpf-rs/commit/855eb8422e98e4632d433d5fbf065ab703674fbf. But that does not cover all issues: you can still have conflicts between a...
Yes, there is no particular reason other than "nobody has implemented [or asked for] it". Feel free to open a pull request if you decide to work on it or...
To the degree I can tell the headers will be extracted somewhere below the target directory. How you set that is up to you and depends on how you generate...
Seems as if `vsprintf` failed to build? Can you report it there?
> By the way, I modified the libbpf-sys-1.4.1+v1.4.0/build.rs otherwise, I can't pass the compilation. Feel free to open a pull request there.