https://bugs.kde.org/show_bug.cgi?id=402833
--- Comment #16 from Olly Betts <ojwbetts+...@gmail.com> --- (In reply to Paul Floyd from comment #15) > Also in your libc, is there more than one function using the same address as > __memmove_chk? (And specifically, is __memcpy_chk the same as __memmove_chk). nm fails to list symbols for me: $ nm /lib/x86_64-linux-gnu/libc.so.6 nm: /lib/x86_64-linux-gnu/libc.so.6: no symbols However someone else previously reported the problem being due to symbols having the same address in the ticket marked as a duplicate of this one - see https://bugs.kde.org/show_bug.cgi?id=453084#c9 : $ nm /lib64/libc.so.6 | grep "__mem\(cpy\|move\)_chk_sse2_unaligned$" 00000000000b9c50 t __memcpy_chk_sse2_unaligned 00000000000b9c50 t __memmove_chk_sse2_unaligned $ nm /lib64/libc.so.6 | grep "__mem\(cpy\|move\)_chk_avx_unaligned$" 00000000001828a0 t __memcpy_chk_avx_unaligned 00000000001828a0 t __memmove_chk_avx_unaligned -- You are receiving this mail because: You are watching all bug changes.
