Messages in this thread | | | Subject | Re: perf backtraces off-by-1 | From | Peter Zijlstra <> | Date | Tue, 28 Aug 2012 18:34:03 +0200 |
| |
On Sun, 2012-08-26 at 10:52 -0700, Arun Sharma wrote: > On 8/26/12 9:10 AM, Peter Zijlstra wrote: > > On Fri, 2012-08-24 at 15:13 -0700, Arun Sharma wrote: > > > >> One option is to support > >> this for user mode only, with code to detect signal frames. Any other > >> ideas? > >> > > I guess we'd need to see what that patch would look like... :-) > > > > It used to look like this: > > http://git.savannah.gnu.org/gitweb/?p=libunwind.git;a=commitdiff;h=92cc7fd78a5a79c4bb5f85bfb7d7fb025df9cd5a
Hmm, that's not too bad, but a long stretch from pretty ;-)
How would you 'encode' this in the perf callchain data?
> These days we just look at dwarf augmentation string: > > http://git.savannah.gnu.org/gitweb/?p=libunwind.git;a=blob;f=src/dwarf/Gfde.c;h=8659624b0320c514057861a259b6efe1b605bbf3;hb=HEAD#l189
Right, except of course we don't have that in kernel..
BTW, are you in San Diego for LinuxCon/LPC etc?
| |