https://bugs.kde.org/show_bug.cgi?id=397083
--- Comment #12 from Mark Wielaard <m...@klomp.org> --- (In reply to Mark Wielaard from comment #11) > It looks like the original c++ issue (which called down to glibc wmemchr) > has been fixed by bug #388862 in 3.14.0 (the reporter used 3.13.0). I think > just intercepting the generic wmemchr (ifunc) is enough, you don't have to > also intercept the internal variants. And I think the same holds for wmemcmp. So you should just have to intercept the main wmemcmp function, not any of its variants (unless those are somehow internally called directly instead of going through the ifunc). -- You are receiving this mail because: You are watching all bug changes.
