Testing valgrind in rawhide (separate valgrind-debuginfo package)

[Richard W.M. Jones]

BTW can you clear up a peculiarity I've noticed in valgrind in
Rawhide?

The symbols reported in the stack traces seem to be mangled in a
strange way, eg:

==11843== 56 bytes in 1 blocks are definitely lost in loss record 6 of 6
==11843==    at 0x4A06409: malloc (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==11843==    by 0x38EAC861F9: strdup (strdup.c:42)
==11843==    by 0x38EC8097C9: setprocattrcon_raw.constprop.3 (procattr.c:241)
==11843==    by 0x38EC8099B7: setprocattrcon.constprop.2 (procattr.c:274)
==11843==    by 0x400955: main (in /tmp/test)

The symbol we're actually calling is 'setsockcreatecon'.  It's not a
macro.  There is no public function called 'setprocattrcon' (although
there is an internal function of that name and setsockcreatecon only
calls this internal functions so there could be some inlining going
on).  And what's with the '.constprop.2' suffix?

In any case, this is a problem because in my valgrind suppressions
file I have to list the mangled name, not the real name.

Test program is here if you want to try it:

https://bugzilla.redhat.com/show_bug.cgi?id=918572

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-p2v converts physical machines to virtual machines.  Boot with a
live CD or over the network (PXE) and turn machines into KVM guests.
http://libguestfs.org/virt-v2v