Citeren "Micah Snyder (micasnyd)" <[email protected]>:
Hi Arjen,
I see what you're talking about. It is a little confounding. We
have a valgrind suppression rule for this specific issue:
https://github.com/Cisco-Talos/clamav-devel/commit/8cfec0b245abfac9564c11012d67b19da004e927
{
binhex-overlapping-memmove
Memcheck:Overlap
fun:__memcpy_chk
fun:memmove
fun:cli_binhex
...
}
Your stack trace has "UnknownInlinedFun " instead of "memmove",
which is ... odd. I suppose feel free to ignore the FP. Adding
another suppression rule with "UnknownInlinedFun" in it doesn't feel
good, nor does spending the effort to reimplement without
overlapping memmoves. Thoughts?
Yup. Your mention of the weird "UnknownInlinedFun " tipped me off. We
use LTO by default in openSUSE Tumbleweed and that seems to be the
culprit here. Without LTO, the valgrind tests are OK. Apparently LTO
strips symbols that are needed for valgrind to see what is going on.
Thanks!
_______________________________________________
clamav-users mailing list
[email protected]
https://lists.clamav.net/mailman/listinfo/clamav-users
Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq
http://www.clamav.net/contact.html#ml
