SUMMARY I am not getting leak summary when executing valgrind.Please let me know in which scenarios/cases leak summary does'nt generate. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
Well assuming valgrind completes successfully only when you disable leak checks, but it would be easier to comment if you showed us what output you do get.
Thanks. However I am not disabling leak checks but still not getting any memory leak summary. Wondering what could be the scenarios when memory leak summary is not generated in logs. I am getting below valgrind logs Conditional jump or move depends on uninitialised value(s) at 0xABCDEF: policy_status (xxxx.c: 1189) by 0xBCDEFG: requests (xxxx.c:11340) Invalid read of size 4 at 0xBBBBBBB: Open_state (yyyyyy.c:1111413) by 0xCCCCCC: calling_function (yyyyyy.c:11144)
Can you tell us more? Which Linux distribution? Packaged or self-built Valgrind? Valgrind options used? Could you also attach the full Valgrind output?
And could you also post the _full_ log summary. I would expect something like ==2604== HEAP SUMMARY: ==2604== in use at exit: 8,936 bytes in 5 blocks ==2604== total heap usage: 84 allocs, 79 frees, 25,537 bytes allocated ==2604== ==2604== LEAK SUMMARY: ==2604== definitely lost: 2,448 bytes in 1 blocks ==2604== indirectly lost: 2,192 bytes in 2 blocks ==2604== possibly lost: 0 bytes in 0 blocks ==2604== still reachable: 4,296 bytes in 2 blocks ==2604== suppressed: 0 bytes in 0 blocks ==2604== Rerun with --leak-check=full to see details of leaked memory ==2604== ==2604== For lists of detected and suppressed errors, rerun with: -s ==2604== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
Not enough detail to do anything with this.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!