https://bugs.kde.org/show_bug.cgi?id=378293
Philippe Waroquiers <philippe.waroqui...@skynet.be> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |philippe.waroquiers@skynet.
| |be
--- Comment #2 from Philippe Waroquiers <philippe.waroqui...@skynet.be> ---
Yes, a small reproducer would be nice.
Alternatively, you could use gdb + vgdb and investigate
why valgrind believes the leaked memory is still reachable, using the
monitor commands
leak_check
block_list
who_points_at
--
You are receiving this mail because:
You are watching all bug changes.
