[valgrind] [Bug 371471] Valgrind complains about non legit memory leaks on placement new (C++)

https://bugs.kde.org/show_bug.cgi?id=371471 Tom Hughes changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[valgrind] [Bug 371471] Valgrind complains about non legit memory leaks on placement new (C++)

https://bugs.kde.org/show_bug.cgi?id=371471 --- Comment #5 from Brian Teixeira --- Sorry, I forgot to mention that you need to include to make it compile. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 371471] Valgrind complains about non legit memory leaks on placement new (C++)

https://bugs.kde.org/show_bug.cgi?id=371471 --- Comment #4 from Tom Hughes --- I'm pretty sure it's not the same anyway as the other bug is about static objects, and there are none here. This is almost certainly something different - the fact that it is reporting two allocations

[valgrind] [Bug 371471] Valgrind complains about non legit memory leaks on placement new (C++)

https://bugs.kde.org/show_bug.cgi?id=371471 --- Comment #3 from Tom Hughes --- Also that code doesn't even compile: bericote [/tmp] % g++ -std=c++14 -o x x.cpp x.cpp: In function ‘int main()’: x.cpp:12:17: error: no matching function for call to ‘operator new(sizetype, A*&)’

[valgrind] [Bug 371471] Valgrind complains about non legit memory leaks on placement new (C++)

https://bugs.kde.org/show_bug.cgi?id=371471 Tom Hughes changed: What|Removed |Added CC||t...@compton.nu --- Comment #2

[valgrind] [Bug 371471] Valgrind complains about non legit memory leaks on placement new (C++)

https://bugs.kde.org/show_bug.cgi?id=371471 Markus Trippelsdorf changed: What|Removed |Added CC|