https://bugs.kde.org/show_bug.cgi?id=463514
Bug ID: 463514 Summary: Valgrind not detecting the leaks. Classification: Developer tools Product: valgrind Version: 3.13.0 Platform: Android OS: Android 5.x Status: REPORTED Severity: major Priority: NOR Component: memcheck Assignee: jsew...@acm.org Reporter: shivaraju173ponnag...@gmail.com Target Milestone: --- Hello, We have a target machine which is an arm 32-bit Android device. And we tried to check the leaks on some essential services for our product. So we choose the Valgrind for our kind of testing. But before proceeding, we want to test the one sample application with memory leaks in it. And run the application on top Valgrind in-arm devices but the leaks were not detected through the Valgrind. Can anyone help me out with this issue? Test Application:- #include <stdio.h> #include <stdlib.h> #include <string.h> #include <unistd.h> int leak_func(void){ char *ptr = NULL; ptr = (char *) calloc(1,20); ptr = "Hello World\n"; printf("%s \n",ptr); return 0; } int main(void){ int i=1; printf("%s: Invoked\n",__func__); leak_func(); while(i++) sleep(1); return 0; } compiled and pushed the above memory leak application into the arm platform device. #valgrind --tool=memcheck --leak-check=full --show-leak-kinds=all --show-reachable=yes --track-fds=yes --trace-children=yes --track-origins=yes --smc-check=all --extra-debug-info-path=path --log-file=/data/local/data.txt -v /system/bin/<memory Leak app> Observations:- the leaks were not detected with Valgrind. ==10143== ==10143== LEAK SUMMARY: ==10143== definitely lost: 0 bytes in 0 blocks ==10143== indirectly lost: 0 bytes in 0 blocks ==10143== possibly lost: 48 bytes in 1 block ==10143== still reachable: 14,843 bytes in 40 blocks ==10143== suppressed: 0 bytes in 0 blocks ==10143== SOFTWARE/OS VERSIONS Host machine Linux:- Linux 5.14.0-1054-oem #61-Ubuntu SMP Fri Oct 14 13:05:50 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Target machine:-Linux Version = 3.4.0 -- You are receiving this mail because: You are watching all bug changes.