https://bugs.kde.org/show_bug.cgi?id=402833
--- Comment #20 from Mark Wielaard <m...@klomp.org> --- (In reply to Paul Floyd from comment #19) > (In reply to Olly Betts from comment #18) > > $ nm -D /usr/lib/x86_64-linux-gnu/libc.so.6|grep 0000000000119f80 > > 0000000000119f80 i __memcpy_chk@@GLIBC_2.3.4 > > $ nm -D /usr/lib/x86_64-linux-gnu/libc.so.6|grep 000000000011a090 > > 000000000011a090 i __memmove_chk@@GLIBC_2.3.4 > > That's not what I was expecting. If the memmove was inlined and > __memcpy_chk and __memmove_chk are aliases then Memcheck > will only use one of them (__memcpy_chk from the errors you got). Note that the "i" means ifunc. So they get resolved at runtime through an ifunc call. It depends on cpu features to which this ifunc resolves. So it could very well be that they resolve to the same address at runtime on one machine, but not on another. > If that's the case then your problem was probably fixed by Mark in October > 2023: > > 39c447e4a9 (Bart Van Assche 2013-11-24 17:48:13 +0000 1716) > /*-------------------- memcpy_chk --------------------*/ > 39c447e4a9 (Bart Van Assche 2013-11-24 17:48:13 +0000 1717) > 53e101f562 (Mark Wielaard 2023-10-30 23:30:06 +0100 1718) /* See > https://bugs.kde.org/show_bug.cgi?id=402833 > 53e101f562 (Mark Wielaard 2023-10-30 23:30:06 +0100 1719) why we > disable the overlap check on x86_64. */ > 53e101f562 (Mark Wielaard 2023-10-30 23:30:06 +0100 1720) #if > defined(VGP_amd64_linux) > 53e101f562 (Mark Wielaard 2023-10-30 23:30:06 +0100 1721) #define > CHECK_OVERLAP 0 > 53e101f562 (Mark Wielaard 2023-10-30 23:30:06 +0100 1722) #else > 53e101f562 (Mark Wielaard 2023-10-30 23:30:06 +0100 1723) #define > CHECK_OVERLAP 1 > 53e101f562 (Mark Wielaard 2023-10-30 23:30:06 +0100 1724) #endif > > Try using Valgrind 3.23 and see if the problem goes away. yeah, that was the workaround for this bug. But that simply means we don't do any overlap checking on x86_64, which is still a bug :{ -- You are receiving this mail because: You are watching all bug changes.
