https://bugs.kde.org/show_bug.cgi?id=324013 --- Comment #5 from Oswald Buddenhagen --- it's unreasonable to harden the code against each possible abuse. latest when memory corruption comes into play, there is no way to get it right. the correct reaction would be refusing to start the process, a condition which is more likely to be tested by the user. -- You are receiving this mail because: You are watching all bug changes.