I suspect the dwarf issue from the post is just missing debug info for some library, or too deep stacks. But leaving that aside, for profiling, dwarf is just v

I suspect the dwarf issue from the post is just missing debug info for some library, or too deep stacks. But leaving that aside, for profiling, dwarf is just very expensive (perf, where the data volume explodes, due to copying stacks) or not available (bpf stacks), because the unwinding has to happen in the kernel. Even if the kernel had a dwarf unwinder, it's vastly more expensive to do that, compared to unwinding via frame pointers. Try running a system wide profile on larger and busy box. Dwarf based call graphs are basically not usable. The profile quickly is ginormous, and viewing profiles is extremely slow.