[valgrind] [Bug 428716] VEX/useful/smchash.c:39:16: error: Memory leak: gb [memleak]

2021-02-20 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=428716 --- Comment #8 from Mark Wielaard --- commit 7967aea84b920d304b99fab60a612740854bd877 Author: Paul Floyd Date: Sun Nov 8 08:00:36 2020 +0100 Bug 478716 - cppcheck detects potential leak in VEX/useful/smchash.c -- You are receiving this mail

[valgrind] [Bug 428716] VEX/useful/smchash.c:39:16: error: Memory leak: gb [memleak]

2020-11-08 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=428716 --- Comment #7 from Paul Floyd --- Oh well. It's already gone in. A bit less noise next time someone runs a static analysis tool on the code. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 428716] VEX/useful/smchash.c:39:16: error: Memory leak: gb [memleak]

2020-11-08 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=428716 Julian Seward changed: What|Removed |Added CC||jsew...@acm.org --- Comment #6 from Julian

[valgrind] [Bug 428716] VEX/useful/smchash.c:39:16: error: Memory leak: gb [memleak]

2020-11-07 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=428716 Paul Floyd changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED

[valgrind] [Bug 428716] VEX/useful/smchash.c:39:16: error: Memory leak: gb [memleak]

2020-11-07 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=428716 --- Comment #5 from Paul Floyd --- It's simple to build: gcc -g -o smchash smchash.c Running it is a bit more complicated. You need to generate in input file to test first, say something like this ../../vg-in-place --trace-notabove=1

[valgrind] [Bug 428716] VEX/useful/smchash.c:39:16: error: Memory leak: gb [memleak]

2020-11-07 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=428716 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org --- Comment #4 from Mark

[valgrind] [Bug 428716] VEX/useful/smchash.c:39:16: error: Memory leak: gb [memleak]

2020-11-07 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=428716 Paul Floyd changed: What|Removed |Added Assignee|jsew...@acm.org |pa...@free.fr Ever confirmed|0

[valgrind] [Bug 428716] VEX/useful/smchash.c:39:16: error: Memory leak: gb [memleak]

2020-11-07 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=428716 --- Comment #2 from dcb...@hotmail.com --- (In reply to Paul Floyd from comment #1) > Did you come across this just by looking at the code? Or using a static > analysis tool? Option 2. Static analyser cppcheck. -- You are receiving this mail

[valgrind] [Bug 428716] VEX/useful/smchash.c:39:16: error: Memory leak: gb [memleak]

2020-11-07 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=428716 --- Comment #1 from Paul Floyd --- Did you come across this just by looking at the code? Or using a static analysis tool? Or a runtime error? The change looks safe to make. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 428716] VEX/useful/smchash.c:39:16: error: Memory leak: gb [memleak]

2020-11-05 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=428716 Paul Floyd changed: What|Removed |Added CC||pa...@free.fr -- You are receiving this mail