https://bugs.kde.org/show_bug.cgi?id=374568
--- Comment #2 from Eugene Shalygin <eugene.shalygin+bugzilla....@gmail.com> --- I was using QtCurve for many years too, but now I check my apps using GCC's sanitizer. This is the reason, I believe. The first problem (memcmp()) was manifesting itself when client code was compiled with the address sanitizer, but then I tried to compile QtCurve itself with it, and this one appeared. I'm using this change for a day only; without it, every touch of any app menu lead to a crash, while now it does not. Did not try Valgrind yet. -- You are receiving this mail because: You are watching all bug changes.
