Testing valgrind in rawhide (separate valgrind-debuginfo package)

[Kevin Kofler]

Mark Wielaard wrote:
> Aha, thanks. Yes using DWARF might help getting more user
> friendly/recognizable names.
> 
> Though note that the name we were really looking for was
> setsockcreatecon, since that is what was called from main. I think that
> one is doing a tail-call to setprocattrcon.constprop.2 so might not
> easily be available in the backtrace. If you compile and run Richard's
> reproducer from https://bugzilla.redhat.com/show_bug.cgi?id=918572 and
> break at the strdup call, can you get a backtrace from gdb with
> setsockcreatecon in it?
> 
> Also using DWARF .debug_info will only work if it is available. By
> default valgrind doesn't require DWARF, it uses only the symbol table. I
> can look in extending valgrind to use the DWARF info when available for
> matching suppressions, but that might mean a suppression only works when
> the debuginfo is installed (and it might make valgrind even slower).

To go from setprocattrcon.constprop.2 (the ELF symbol name) to 
setprocattrcon (the name in DWARF), you don't need the DWARF at all, just a 
s/\.constprop\.[0-9]+$//g. :-)

        Kevin Kofler