emerge valgrind && emerge -1 libdrm [snip] checking for native atomic primitives... Intel checking for PCIACCESS... yes checking for VALGRIND... yes checking that generated files are newer than configure... done configure: creating ./config.status [snap] I do not exactly know what this does. (I think it will enable suppressions for certain calls to not trigger false positives, e.g. "hidden" frees etc.) But I think there should be a USE-Flag to toggle the DEP. A quick grep in my build logs showed quite some hits: vim-core, notmuch, udev, mpd, gst-plugins-ffmpeg, systemd, xapian, ruby. Also gcc checks for valgrind, but I do not have a gcc-build.log from after I first installed valgrind, so those checks return "no". Probably a TRACKER bug would be great to find all those automagics. And add a global valgrind USE-Flag.
(In reply to Franz Fellner from comment #0) > I do not exactly know what this does. (I think it will enable suppressions > for certain calls to not trigger false positives, e.g. "hidden" frees etc.) This is right. > But I think there should be a USE-Flag to toggle the DEP. Does anyone know how the emitted suppressions work?
should be all set now in the tree; thanks for the report! Commit message: Add USE=valgrind to control inclusion of memory hints http://sources.gentoo.org/x11-libs/libdrm/libdrm-2.4.59-r1.ebuild?rev=1.1 http://sources.gentoo.org/x11-libs/libdrm/metadata.xml?r1=1.2&r2=1.3