https://bugs.kde.org/show_bug.cgi?id=415293
Bug ID: 415293
Summary: Incorrect call-graph tracking due to new
_dl_runtime_resolve_xsave* functions
Product: valgrind
Version: 3.15 SVN
Platform: RedHat RPMs
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: callgrind
Assignee: josef.weidendor...@gmx.de
Reporter: paulo.cesar.pereira.de.andr...@gmail.com
Target Milestone: ---
Newer glibc have alternate ld.so _ld_runtime_resolve functions.
Namely _dl_runtime_resolve_xsave and _dl_runtime_resolve_xsave'2
Those exist to save the full AVX registers, for applications that somewhat
use an 'extended' x86_64 ABI.
The problem is that applications need to run with LD_BIND_NOW set for
kcachegrind to have some more meaningful usage.
I believe callgrind/fn.c should be extended to handle these new ld.so
symbols.
(BTW, it appears there is a minor typo in the comments of callgrind/fn.c,
that tell about _ld_runtime_resolve, but check for _dl_runtime_resolve).
--
You are receiving this mail because:
You are watching all bug changes.
