https://bugs.kde.org/show_bug.cgi?id=522497
--- Comment #3 from Mark Wielaard <[email protected]> --- (In reply to yury.khrustalev from comment #2) > This patch > https://inbox.sourceware.org/libc-alpha/20260701131617.3073925-1-yury. > [email protected]/ makes the error explicit. Without this patch Valgrind > seems to be working fine (at least when I tested it with the new Glibc it > work for the basic uses cases that I tried) but it doesn't change the fact > that at some point at start up Valgrind calls the 'malloc' symbol without > resolving it as a GNU ifunc. The fail early patch above makes this error > explicit. Interesting. Do you happen to have a backtrace of where exactly this invocation of the malloc ifunc resolver takes place? So maybe we do that while it is unnecessary because we already intercept the malloc call (and should then never call it directly) so things appear to work fine. -- You are receiving this mail because: You are watching all bug changes.
