[valgrind] [Bug 345307] Please suppress warning about "still reachable" memory when using libstdc++ from gcc 5

https://bugs.kde.org/show_bug.cgi?id=345307 Ivo Raisr changed: What|Removed |Added CC||iv...@ivosh.net -- You are receiving this mail

[valgrind] [Bug 345307] Please suppress warning about "still reachable" memory when using libstdc++ from gcc 5

https://bugs.kde.org/show_bug.cgi?id=345307 --- Comment #4 from Ivo Raisr --- I hit this also on Solaris 12 which now ships gcc 5.3. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 345307] Please suppress warning about "still reachable" memory when using libstdc++ from gcc 5

https://bugs.kde.org/show_bug.cgi?id=345307 Ivo Raisr changed: What|Removed |Added Version|3.10.0 |3.12 SVN --- Comment #5 from Ivo Raisr

[valgrind] [Bug 345307] Please suppress warning about "still reachable" memory when using libstdc++ from gcc 5

https://bugs.kde.org/show_bug.cgi?id=345307 --- Comment #6 from Ivo Raisr --- Created attachment 97339 --> https://bugs.kde.org/attachment.cgi?id=97339&action=edit patch for Solaris -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 345307] Please suppress warning about "still reachable" memory when using libstdc++ from gcc 5

https://bugs.kde.org/show_bug.cgi?id=345307 Ivo Raisr changed: What|Removed |Added Ever confirmed|0 |1 Severity|minor

[valgrind] [Bug 345307] Warning about "still reachable" memory when using libstdc++ from gcc 5

https://bugs.kde.org/show_bug.cgi?id=345307 Ivo Raisr changed: What|Removed |Added Summary|Please suppress warning |Warning about "still |

[valgrind] [Bug 345307] Warning about "still reachable" memory when using libstdc++ from gcc 5

https://bugs.kde.org/show_bug.cgi?id=345307 --- Comment #8 from Ivo Raisr --- Created attachment 97556 --> https://bugs.kde.org/attachment.cgi?id=97556&action=edit patch for Linux and Solaris calling __gnu_cxx::__freeres from libstdc++ This is fix for the Valgrind side. Fix for

[valgrind] [Bug 345307] Warning about "still reachable" memory when using libstdc++ from gcc 5

https://bugs.kde.org/show_bug.cgi?id=345307 --- Comment #9 from Ivo Raisr --- Regression testing on Linux and Solaris went fine. Together with patch for https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69945 we see now: ==1862== HEAP SUMMARY: ==1862== in use at exit: 0 bytes in 0 blocks ==1862

[valgrind] [Bug 359871] Incorrect mask handling in ppoll

https://bugs.kde.org/show_bug.cgi?id=359871 Ivo Raisr changed: What|Removed |Added CC||iv...@ivosh.net --- Comment #2 from Ivo Raisr

[valgrind] [Bug 359871] Incorrect mask handling in ppoll

https://bugs.kde.org/show_bug.cgi?id=359871 Ivo Raisr changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED

[valgrind] [Bug 359871] Incorrect mask handling in ppoll

https://bugs.kde.org/show_bug.cgi?id=359871 Ivo Raisr changed: What|Removed |Added Attachment #97584|0 |1 is obsolete

[valgrind] [Bug 359871] Incorrect mask handling in ppoll

https://bugs.kde.org/show_bug.cgi?id=359871 --- Comment #6 from Ivo Raisr --- Steven, thank you for the test case provided and a suggested fix. Indeed, simple things are very often also effective. I will prepare patch for Linux as well and have that reviewed. -- You are receiving this mail

[valgrind] [Bug 359871] Incorrect mask handling in ppoll

https://bugs.kde.org/show_bug.cgi?id=359871 --- Comment #7 from Ivo Raisr --- The attached patch has two problems: - it modifies a client memory which may be read-only (see for example bugs for modifying env) - it modifies a client memory and does not restore the changes after syscall -- You

<    2   3   4   5   6   7