Hi Milian, On Sat, Jan 28, 2017 at 10:20 PM, Milian Wolff <[email protected]> wrote: > Hey all, > > now that libunwind is becoming more alive again, could we get the > unw_backtrace_skip functionality upstream? For those who are unacquainted with > it: > > It gives you the behavior of unw_backtrace, but skips the first N frames, see > e.g.: > > https://gist.github.com/mikesart/8365549 > > This is often required in profilers to skip frames introduced by the profiler > itself.
I don't see the what this adds as a feature, what cant already be done by the caller after calling unw_backtrace itself? As ignoring the first 'n' entries in the resulting backtrace buffer has the same effect and it wont get faster. What would be a enhancement for the user, would be an option to skip everything till the first (or last) entered signal frame on the stack. As that includes only the part which triggered the signal, but not the signal handler. BTW, why is 'unw_backtrace' the only symbol without the usual '_U' prefix, it is the only one with the 'unw_' prefix. Bert > > Cheers _______________________________________________ Libunwind-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/libunwind-devel
