https://bugs.kde.org/show_bug.cgi?id=400783
--- Comment #3 from Tom Hughes <t...@compton.nu> --- The only reference to valgrind in that stack trace is to our replacement free routine which has detected the problem - the actual problem is in the dynlink.c code about that which has apparently passed an invalid pointer to free. -- You are receiving this mail because: You are watching all bug changes.
