https://bugs.kde.org/show_bug.cgi?id=420780
Carl Love <c...@us.ibm.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |c...@us.ibm.com
Status|REPORTED |RESOLVED
Resolution|--- |FIXED
--- Comment #2 from Carl Love <c...@us.ibm.com> ---
Compiled the included test case and ran on the current upstream Valgrind as of
9/1/2021. The test case seems to run fine now.
valgrind ./valgrind-420780
==2869120== Memcheck, a memory error detector
==2869120== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==2869120== Using Valgrind-3.18.0.GIT and LibVEX; rerun with -h for copyright
info
==2869120== Command: ./valgrind-420780
==2869120==
==2869120==
==2869120== HEAP SUMMARY:
==2869120== in use at exit: 16 bytes in 1 blocks
==2869120== total heap usage: 1 allocs, 0 frees, 16 bytes allocated
==2869120==
==2869120== LEAK SUMMARY:
==2869120== definitely lost: 16 bytes in 1 blocks
==2869120== indirectly lost: 0 bytes in 0 blocks
==2869120== possibly lost: 0 bytes in 0 blocks
==2869120== still reachable: 0 bytes in 0 blocks
==2869120== suppressed: 0 bytes in 0 blocks
==2869120== Rerun with --leak-check=full to see details of leaked memory
==2869120==
==2869120== For lists of detected and suppressed errors, rerun with: -s
==2869120== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0
Compiled the test case wth
gcc --version
gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
Marking the issue resolved.
--
You are receiving this mail because:
You are watching all bug changes.
