[valgrind] [Bug 378293] False Negative on memory leak
https://bugs.kde.org/show_bug.cgi?id=378293 Darshit Shahchanged: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #4 from Darshit Shah --- Hi Sorry for the delayed response. While trying to create a minimum working example for the bug, I realised that the issue was in how we were using valgrind and not in valgrind itself. The leak was indeed there, but the original memory was allocated by a part of the program which wasn't run under valgrind. Sorry for the noise! -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 378293] False Negative on memory leak
https://bugs.kde.org/show_bug.cgi?id=378293 --- Comment #3 from Philippe Waroquiers--- (In reply to Darshit Shah from comment #0) > I would love to help you debug this issue and create a minimal example / dig > into valgrind, but as of now I have no idea where to start. ... > If there is any other information I can provide > / debug, do let me know. Any news/feedback following suggestions in comment 2 and comment 3 ? Thanks -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 378293] False Negative on memory leak
https://bugs.kde.org/show_bug.cgi?id=378293 Philippe Waroquierschanged: What|Removed |Added Assignee|jsew...@acm.org |philippe.waroquiers@skynet. ||be -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 378293] False Negative on memory leak
https://bugs.kde.org/show_bug.cgi?id=378293 Philippe Waroquierschanged: What|Removed |Added CC||philippe.waroquiers@skynet. ||be --- Comment #2 from Philippe Waroquiers --- 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.
[valgrind] [Bug 378293] False Negative on memory leak
https://bugs.kde.org/show_bug.cgi?id=378293 Ivo Raisrchanged: What|Removed |Added CC||iv...@ivosh.net --- Comment #1 from Ivo Raisr --- Thank you for the report. Please start with providing a simple reproducer. File tests/test-metalink.c has around 300 lines and file tests/libtest.c almost 1000 lines. If you can squash it down to lets say 50-100, then it would great! -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 378293] False Negative on memory leak
https://bugs.kde.org/show_bug.cgi?id=378293 Darshit Shahchanged: What|Removed |Added CC||dar...@gmail.com -- You are receiving this mail because: You are watching all bug changes.