Re: Sp! Re: Perf Script Erroneous User Stack Trace

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


Hi Milian,
Firstly, thanks for the detailed answer! But, it seems that you missed the first thread. There, I said that, I manually used perf_event_open() which dumps raw IPs (which are not unwound). But those raw IPs, themselves were erroneous. Many callchains were single element ones, containing only the innermost RIP, while many others were truncated and not rooted at "_start" or "__GI___clone()".


On 2020-06-16 20:50, Milian Wolff wrote:

On Dienstag, 16. Juni 2020 16:37:08 CEST ahmadkhorrami wrote:

The problem doesn't seems to be caused by the assembly code. I checked
the execution in GDB, and put breakpoint at
"x264_pixel_avg_w16_avx2+0x4" and ignored with 10, 100, 1000, 10000 and 100000 occurrences. But, in all cases, GDB, successfully, displayed the
whole backtrace. One of them is as follows:


It seems that, there should be something wrong with the kernel-side
implementation. Could anybody point me to the kernel implementation? I
think it is dumped, here:

But, I do not know where in the kernel, the user call-stack is
Any guesses?

The kernel does not unwind the user call-stack when you use `perf record -- call-graph dwarf`. This is all done in user space at `perf report` time. The
kernel only copies parts of the stack, in your case 64KB.

There are tons of ways that can lead to broken unwinding. To figure out more,
you'll have to dive into `perf report` and try to come with some ideas

a) try to figure out how unwinding should work for that library, does it have .eh_frame or does it need debug information for unwinding? If the latter - run `strace -e file -f perf script` and check if the separate debug information
files are found and loaded by perf.
b) run `perf script -v` and inspect the log for your first broken sample - is
there anything in it that may indicate the reason for the issue?
c) try elfutils instead of libunwind for unwinding, does that make a
d) dive even deeper into the code to see where and why it fails, potentially
even within libunwind

Note that GDB uses a completely different unwinder than perf. Libunwind is pretty good, but GDB has even better fallbacks to figure out backtraces. I mean it often even works after (partial) stack corruption there ;-) So just
saying "it works in GDB" doesn't help us too much...

Good luck!

[Index of Archives]     [Linux USB Development]     [Linux USB Development]     [Linux Audio Users]     [Yosemite Hiking]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux