https://bugs.kde.org/show_bug.cgi?id=402833
--- Comment #19 from Paul Floyd <pjfl...@wanadoo.fr> --- (In reply to Olly Betts from comment #18) > I'm using valgrind via a testsuite harness and valgrind's output unhelpfully > gets interleaved with other output so it was much much easier to just cut > and paste the three lines that actually seemed relevant. I'll try to get > the full clean output for you, but there was just the banner lines before > that and after that was into functions in the library code being tested. I'd like to see if the call to memmove is getting inlined. We do de-inlining for error reports but not at runtime. That means that if memmove is inlined memcheck won't redirect it. Instead it will redirect __memmove_chk > $ 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). 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. -- You are receiving this mail because: You are watching all bug changes.
