https://bugs.kde.org/show_bug.cgi?id=402833
--- Comment #18 from Olly Betts <ojwbetts+...@gmail.com> --- (In reply to Paul Floyd from comment #17) > This is getting frustrating. > > I keep asking questions and you keep (incorrectly) second guessing something > else. > > I'm still waiting to see the exact error. I don't want you to second guess > that it means just the top two elements in the callstack. I just missed you'd posted two replies earlier. > Full Memcheck errors are delimited by lines with just "==PID==" where PID is > a number representing the process ID. It's everything between those > delimiting lines that I want to see. Is that clear? 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. > Secondly I gave an example using "nm -D". You interpreted that as "nm" > without "-D". Then you copied some output from Fedora whilst you are using > Debian. Sorry, I managed to miss the `-D` - there are no other symbols with the same address as either __memcpy_chk or __memmove_chk it seems: $ 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 -- You are receiving this mail because: You are watching all bug changes.
