[valgrind] [Bug 438647] Not getting memory leak summary

2023-02-11 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=438647

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #7 from Bug Janitor Service  ---
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!

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 438647] Not getting memory leak summary

2023-01-27 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=438647

--- Comment #6 from Bug Janitor Service  ---
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!

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 438647] Not getting memory leak summary

2023-01-13 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=438647

Paul Floyd  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|REPORTED|NEEDSINFO

--- Comment #5 from Paul Floyd  ---
Not enough detail to do anything with this.

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 438647] Not getting memory leak summary

2021-07-18 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=438647

--- Comment #4 from Paul Floyd  ---
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)

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 438647] Not getting memory leak summary

2021-06-20 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=438647

Paul Floyd  changed:

   What|Removed |Added

 CC||pjfl...@wanadoo.fr

--- Comment #3 from Paul Floyd  ---
Can you tell us more?

Which Linux distribution?
Packaged or self-built Valgrind?
Valgrind options used?

Could you also attach the full Valgrind output?

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 438647] Not getting memory leak summary

2021-06-14 Thread amita dwivedi
https://bugs.kde.org/show_bug.cgi?id=438647

--- Comment #2 from amita dwivedi  ---
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 (.c: 1189)
by 0xBCDEFG: requests (.c:11340)

Invalid read of size 4
at 0xBBB: Open_state (yy.c:413)
 by 0xCC: calling_function (yy.c:11144)

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 438647] Not getting memory leak summary

2021-06-14 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=438647

Tom Hughes  changed:

   What|Removed |Added

 CC||t...@compton.nu

--- Comment #1 from Tom Hughes  ---
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.

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 438647] Not getting memory leak summary

2021-06-14 Thread amita dwivedi
https://bugs.kde.org/show_bug.cgi?id=438647

amita dwivedi  changed:

   What|Removed |Added

Summary|Not getting leak summary|Not getting memory leak
   ||summary

-- 
You are receiving this mail because:
You are watching all bug changes.