https://bugs.kde.org/show_bug.cgi?id=458118
--- Comment #4 from Michael Barth <spirrw...@gmail.com> --- I do believe it is a result of the destructor being called and not specifically delete or free. Using placement new with malloc'd memory and calling the destructor manually yields the same kind of segmentation fault. In which case, that kinda stinks. Oh well, thank you anyway! -- You are receiving this mail because: You are watching all bug changes.
