Yale Zhang <[email protected]> writes:

> [...]
> I've already tried lowering the size of each sample from 8KiB to 512,
> but that only allows storing 2 or 3 parent function calls, which isn't
> enough for me.
>
> "don't use dwarf unwinding."
> The main reason I'm trying to switch from Zoom to perf is because it
> supports dwarf unwinding! [...]

You may wish to try systemtap.  Its backtracing uses in-situ dwarf
unwinding, and is pretty fast.  Each sample costs not 4K+ of stack
snapshots, but a hexadecimal pc-list or optionally symbolic backtrace
string.  The downside is that the programs that you may be backtracing
need to be identified at stap invocation - ahead of time - via
something like:

  % stap -d /bin/foo -d /usr/lib64/libbar.so --ldd --all-modules SCRIPT.stp

See e.g. https://sourceware.org/systemtap/examples/#profiling/pf4.stp

- FChE
--
To unsubscribe from this list: send the line "unsubscribe linux-perf-users" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to