[valgrind] [Bug 469565] valgrind not detecting simple leak with malloc(In Arm System)

2023-05-14 Thread Sam James
https://bugs.kde.org/show_bug.cgi?id=469565 Sam James changed: What|Removed |Added CC||s...@gentoo.org -- You are receiving this mail bec

[valgrind] [Bug 469565] valgrind not detecting simple leak with malloc(In Arm System)

2023-05-12 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=469565 --- Comment #9 from Paul Floyd --- Debuginfo will help, but I think that there is a more fundamental problem. Can you post the "Program Header" from running "objdump -p" on your test exe? This is what I get on a Centos 7.6 aarch64 machine (Cavium Thun

[valgrind] [Bug 469565] valgrind not detecting simple leak with malloc(In Arm System)

2023-05-11 Thread oooo
https://bugs.kde.org/show_bug.cgi?id=469565 --- Comment #8 from --- Indeed, after I uploaded libc-2.30.so in the /lib of arm linux to the local, and then i used the arm-linux-gnueabihf-nm command to read the symbol information in it and found that it was empty tu@ubuntu:~/Software/tmp$ arm-

[valgrind] [Bug 469565] valgrind not detecting simple leak with malloc(In Arm System)

2023-05-11 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=469565 --- Comment #7 from Paul Floyd --- (In reply to Tom Hughes from comment #6) > It shouldn't be possible to strip libc.so in a way that removes a public > symbol like malloc - it must at least be in the dynamic symbol table or the > dynamic linker couldn'

[valgrind] [Bug 469565] valgrind not detecting simple leak with malloc(In Arm System)

2023-05-11 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=469565 --- Comment #6 from Tom Hughes --- It shouldn't be possible to strip libc.so in a way that removes a public symbol like malloc - it must at least be in the dynamic symbol table or the dynamic linker couldn't work. -- You are receiving this mail becaus

[valgrind] [Bug 469565] valgrind not detecting simple leak with malloc(In Arm System)

2023-05-11 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=469565 --- Comment #5 from Paul Floyd --- You are not reading any symbols from /lib/libc-2.30.so Is it stripped? On amd64 'file' tells me file /usr/lib64/libc-2.17.so /usr/lib64/libc-2.17.so: ELF 64-bit LSB shared object, x86-64, version 1 (GNU/Linux), dynam

[valgrind] [Bug 469565] valgrind not detecting simple leak with malloc(In Arm System)

2023-05-11 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=469565 --- Comment #4 from Tom Hughes --- Are using a statically linked C library? -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 469565] valgrind not detecting simple leak with malloc(In Arm System)

2023-05-11 Thread oooo
https://bugs.kde.org/show_bug.cgi?id=469565 --- Comment #3 from --- (In reply to Paul Floyd from comment #2) > Could you run with --log-file=redir.log --trace-redir=yes and attech the > resulting redir.log here please? sure,thanks for your reply i run with the ./valgrind --leak-check=ful

[valgrind] [Bug 469565] valgrind not detecting simple leak with malloc(In Arm System)

2023-05-10 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=469565 Paul Floyd changed: What|Removed |Added CC||pjfl...@wanadoo.fr --- Comment #2 from Paul Floyd

[valgrind] [Bug 469565] valgrind not detecting simple leak with malloc(In Arm System)

2023-05-10 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=469565 Tom Hughes changed: What|Removed |Added CC||t...@compton.nu --- Comment #1 from Tom Hughes --