https://bugs.kde.org/show_bug.cgi?id=463514
Raju Ponnagani <shivaraju173ponnag...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |shivaraju173ponnagani@gmail
| |.com
--- Comment #2 from Raju Ponnagani <shivaraju173ponnag...@gmail.com> ---
Created attachment 154858
--> https://bugs.kde.org/attachment.cgi?id=154858&action=edit
valgrind report
Yes true. But the leak is a direct leak and should come under "definitely lost"
not "possibly lost".
Possibly lost:-
==10143== 48 bytes in 1 blocks are possibly lost in loss record 31 of 41
==10143== at 0x481E1F0: malloc (vg_replace_malloc.c:298)
==10143== by 0x4CB17B5: android::SharedBuffer::alloc(unsigned int) (in
/system/lib/libutils.so)
==10143== by 0x4CB3D65: android::VectorImpl::_grow(unsigned int, unsigned
int) (in /system/lib/libutils.so)
==10143== by 0x4CB3DF7: android::VectorImpl::insertAt(void const*, unsigned
int, unsigned int) (in /system/lib/libutils.so)
==10143== by 0x4CB426D: android::add_sysprop_change_callback(void (*)(),
int) (in /system/lib/libutils.so)
==10143== by 0x40015B9: __dl__ZN6soinfo12CallFunctionEPKcPFvvE (in
/system/bin/linker)
and for this example, the possible leak is not pointing to the exact
application leak.
and if I ran the same application in the x86_64 platform it's showing an
accurate leak.
Report for the Same application on the X86_64 platform:-
$ Valgrind ./a.out
==468067== Memcheck, a memory error detector
==468067== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==468067== Using Valgrind-3.15.0 and LibVEX; rerun with -h for copyright info
==468067== Command: ./a.out
==468067==
main: Invoked
Hello World
^C==468067==
==468067== Process terminating with default action of signal 2 (SIGINT)
==468067== at 0x49461B4: clock_nanosleep@@GLIBC_2.17 (clock_nanosleep.c:78)
==468067== by 0x494BEC6: nanosleep (nanosleep.c:27)
==468067== by 0x494BDFD: sleep (sleep.c:55)
==468067== by 0x109215: main (in /home/My-Space/Kernel_Test/Leak_Test/a.out)
==468067==
==468067== HEAP SUMMARY:
==468067== in use at exit: 20 bytes in 1 blocks
==468067== total heap usage: 2 allocs, 1 frees, 1,044 bytes allocated
==468067==
==468067== LEAK SUMMARY:
==468067== definitely lost: 20 bytes in 1 blocks
==468067== indirectly lost: 0 bytes in 0 blocks
==468067== possibly lost: 0 bytes in 0 blocks
==468067== still reachable: 0 bytes in 0 blocks
==468067== suppressed: 0 bytes in 0 blocks
==468067== Rerun with --leak-check=full to see details of leaked memory
==468067==
==468067== For lists of detected and suppressed errors, rerun with: -s
==468067== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
-----------------------------------------------------------------------------------
Yes, I tried the latest Valgrind versions 3.16,3.17,3.19, and 3.20. But the
Leak summary is not generating for ARM (32bit) android devices.
Any solution for this issue?
--
You are receiving this mail because:
You are watching all bug changes.
