Felix Geisendörfer

@tutumagi hm, I can't reproduce this issue locally. Can you run this and share the output you get? ``` cat "$(../../go-patch-overlay ./patches)" ```

What does `go1.16 env GOROOT` give you? Did you compile `../../go-patch-overlay` with the same `go1.16` binary? If not, that's probably the cause of this issue.

On behalf of Datadog I want to express our gratitude to the Elastic/Optimyze team for their contributions to continuous profiling in the observability industry, including this proposed donation. As contributors...

> If the SIG is permanent (or very long running/with no clear end goal yet), I think we do not need a document. I think this will be the case...

Thanks for raising this. > In particular for deep stack traces with a high number of similar frames and where only leaf frames are different, That should be most CPU...

@athre0z interesting idea! Do you have an algorithm in mind for encoding the data in this way? A bit of a meta comment: I think it's difficult to evaluate different...

Your algorithm sounds like it could work nicely. That being said, I see two paths forward: 1. Try out new ideas like yours and make sure we get the evaluation...

@tianon thank you so much for your research on this! What about a dedicated debug image as suggested by @otbutz ? Would you consider to include something like this in...

> Debugging the database itself is not what most users of this image are trying to achieve. I think a separate image and thus an opt-in approach is more appropriate....

> but several are then not installable due to version mismatches, which would be due to Debian security updates (which AFAIK, still do not publish debug symbol packages anywhere): FWIW,...