Florian Lehner

> Unknown territory for me: What if a Go executable is dynamically loading shared libraries built with Go? Wouldn't we need the binary filename per frame? No, we don't need...

> Could you add a unit test for the new sequence? So far we don't know the reason that causes this relative offset from RIP. I can name a bunch...

@fabled I did add a unit test with https://github.com/open-telemetry/opentelemetry-ebpf-profiler/pull/890/commits/abc27ccc414ccecf5eb7ed80f08f0cd1eb6d1b93 as described in https://github.com/open-telemetry/opentelemetry-ebpf-profiler/pull/890#issuecomment-3450486920.

Closing, as it is blocked by https://github.com/open-telemetry/opentelemetry-ebpf-profiler/pull/984. Once https://github.com/open-telemetry/opentelemetry-ebpf-profiler/pull/984 is merged, I will open a new PR. Due to changes to EasyCLA I can not apply changes to this branch...

As the OTel Profiling signal is still considered not stable, this step should postponed until the OTel Profiling signal is declared stable. Without a stable OTel Profiling signal, there will...

I think the significant difference here is, that the components you are referring to, are naming the state of their compatibility to the OTel Profiling signal. As far as I...

If OTel collector, that includes eBPF profiler, is build with Go 1.18, then these information are available via [debug.ParseBuildInfo(..)](https://pkg.go.dev/runtime/debug#ParseBuildInfo). They are added by Go by default in `BuildInfo.Settings` with the...

They are vcs information from the latter. But as the latter does have a `go.mod` file, one can point to a specific dependency commit.

I'm unsure wheter or not this change requires a changelog. For the moment, I marked it as `[chore]` as it does not touch a component that is ending up in...

This PR is still pending on https://github.com/open-telemetry/opentelemetry-collector/pull/14252 getting merged.