Another note: the profiling information displayed is the count of different
events from perf, for example cycles and cache misses. Each column is a
different event, and the intensity/shape of the dots on each line is based
on the percentage of that event count for that instruction. We think the
Sorry about the bad layout of images. I dragged them into a triangle layout
but when hitting post it overlayed them like this.
On Thursday, July 28, 2016 at 4:30:00 PM UTC+1, alexande...@arm.com wrote:
>
> New feature in turbolizer allows display of profiling information next to
> instructions,
New feature in turbolizer allows display of profiling information next to
instructions, and in an effort to improve the usability I have a few
different versions of giving a "quick glance" of the information. Currently
undecided on which option is the most preferable, if anyone has feedback it
Hey,
I just landed a new gdb macro "jss" (javascript skip stack) that allows you
to skip a jitted x64 stack:
Program received signal SIGTRAP, Trace/breakpoint trap.
[Switching to Thread 0x7f50d02c4700 (LWP 8152)]
base::debug::(anonymous namespace)::DebugBreak ()
at
