All ticks coming from inside the chrome binary apparently are being
attributed to a single base address:
80.39% chrome [unknown] [.] 0x808711d
0.73% chrome ld-2.11.1.so [.] do_lookup_x
0.55% chrome [kernel.kallsyms] [k] page_fault
I am building with GYP_DEFINES=profiling=1 release_extra_cflags=-fno-
omit-frame-pointer linux_disable_pie=1 target_arch=ia32 (and running
on x64 Linux workstation) and this was fine before.
Is anybody aware of any recent changes that might have caused such
behavior?
Thanks.
--
Vyacheslav Egorov